Name for the new field. Field names must be unique within a template. Although special characters are allowed, they must be URL-encoded in subsequent requests, so it is recommended to use only alphanumeric characters and hyphens if possible.
role_name*string
Role to assign to the field. Role names must be valid, so it is recommended to create roles before fields.
Width of the field. Note that all fields have built-in defaults, and it is recommended that this only be set on text fields.
height?integer
Height of the field. Note that all fields have built-in defaults, and it is recommended that this only be set on text fields.
placeholder?string
Optional placeholder to display in text fields
group?string
For fields that support grouping (radio buttons and check boxes) the value selected will be stored under this name
options?array<>
For dropdown fields, the options to display
default?string
Default value to pre-fill in the field. For checkboxes and radio buttons, true or "true" starts checked. Numbers are stored as text with thousands separators, e.g. "1,234.50". A date field given an ISO 8601 date starts out showing it as MM/dd/yyyy.
readonly?boolean
Whether recipients are prevented from changing the field. May not be combined with required.
Default"false"
validator?string
Name of a validator to apply to the field's value (e.g. "email" or "phone")
data_key?string
Your key for the field's value, such as "applicant.full_name". Fields that show the same value can share a key. Letters, digits, "_", and "-", with "." between levels. Text, date, checkbox, radio, and dropdown fields only.