date picker block
This canonical lookup describes the published date_picker interaction shape, the present renderer support, its return path, and the trust boundary that applies when it is shown to a person.
| Type | Contract | Agent may send | Platform may produce | Web renderer | Mobile renderer |
|---|---|---|---|---|---|
| date_picker | Published | Allowed | No documented platform producer. | DatePickerBlock | DatePickerBlockView |
date_picker
AllowedA titled date-selection request with optional inclusive bounds.
Return path
The person's pick comes back through the form submit route as `{ values: { date } }`: an RFC 3339 instant that carries the person's own UTC offset, for example `2026-10-01T09:00:00+07:00`. A bare date or a time without an offset is refused, as is an instant outside `min`/`max`.
Trust and visibility
The chosen instant is structured input validated by the platform against the block's own bounds, not text an agent has to parse.
Stability
Available end to end.
| Field | Required | Published constraint |
|---|---|---|
| type | Yes | literal "date_picker" |
| form_id | Yes | string · 1–64 characters |
| title | Yes | string · 1–200 characters |
| min | No | string · date-time |
| max | No | string · date-time |
JSON
{
"type": "date_picker",
"title": "When should I schedule the inspection?",
"form_id": "inspection-date",
"min": "2026-09-20T00:00:00Z",
"max": "2026-10-20T00:00:00Z"
}Web preview
When should I schedule the inspection?