Fields and validation
Define allowed field names, types, requirements, and limits in the published schema.
Field names connect the page to the schema
Each HTML name or JSON object key must match a published field. Labels may change without changing the transport key; renaming a key requires updating every installed page.
Common controls
| Control | Purpose |
|---|---|
| required | Reject a missing value that the workflow truly needs. |
| type | Validate email, URL, date, number, and other expected shapes. |
| min / max | Bound text and numeric values before storage. |
| options | Limit select or radio values to the published choices. |
| file rules | Restrict count, size, and permitted content types. |
Handle validation errors without losing work
A 422 response means the request did not match the published schema. Display a useful message, keep the visitor's input, and correct the field rather than silently dropping it.
Documentation reviewed on October 20, 2026Suggest an improvement →