Retrieve all fields configured for a specific template
API key for authentication. Use your API key directly without any prefix (e.g., 'your-api-key'). Bearer prefix is optional but not required.
Template ID
Template fields retrieved successfully
Unique identifier for the field
Name of the field
Type of the field
text, signature, date, checkbox, dropdown, radio_buttons, number, text_area, file, initial Whether the field is required
X coordinate of field position
Y coordinate of field position
Width of the field
Height of the field
Page number where the field is located
x >= 1Variable name for field (used in templates)
Options for dropdown fields
Default date value
Use signing date as default
Group ID for multi-instance fields (e.g., radio button groups)
Formatting rules - currently used for date fields to specify display format
{ "dateFormat": "MMMM dd, yyyy" }Validation rules for field values. Reserved for future use - currently not enforced for any field types.
ID of assigned recipient
Whether this field is read-only (pre-filled before signing). When true, the signer cannot edit the field value.
Static value for read-only fields. Takes precedence over prefilled_data if both are specified. Only applicable when read_only is true.
User attribute to auto-populate when read_only is true. Value is pulled from the assigned recipient's data. Can also reference custom_fields keys defined on the recipient (not limited to enum values). Only applicable when read_only is true and read_only_value is not set.
first_name, last_name, full_name, email, phone_number, company, title, street_address, city, state_province, postal_code, country