> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/elements/fields/date-selector.md).

# Date Selector

The Date Selector field allows users to choose a date from a visual interface.

The `Date Selector` field allows the user to select a date, historical or future. The date value gets stored in the format `YYYY-MM-DD`. You can also configure the date selector to allow the user to pick a specific time of day. In that case, the entry is stored in the format `YYYY-MM-DDTHH:mm:ss`.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FGWHORsH3hzzXXrehpzel%2Fdocs_element-date.png?alt=media&amp;token=62fe8281-6760-41f8-b786-d91e1e1c5000" alt=""><figcaption></figcaption></figure>

### For Developers <a href="#example" id="example"></a>

The Feathery SDK and API reference dropdown fields with `type` equal to `date_selector`. The submitted value is a `string` of length 10, including `-` separators between the month, day, and year. If time selection is enabled, the submitted value is a string of length `19` and also includes the hour, minute, and second.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feathery.io/platform/build-forms/elements/fields/date-selector.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
