Get a form schema
Returns the form’s submittable fields: the field id to use as the payload key, the label, whether the field is required, the value shape to send, and (for picklists) the allowed values. Call this before POST /api/v1/forms/{formId}/submissions instead of copying field ids out of the Introw UI by hand.
Field ids. id is the key to use in the submission’s fields map. Ids are opaque, generated identifiers (for example qkzv8h2m4t6r1yc9pd3sxf70), never human-readable names, and unique per form. They are stable: a field keeps its id across form edits.
Value shapes. dataType is the one field to branch on: it tells you what to send, whether that is a string, a number, a YYYY-MM-DD date, a picklist value, or a file URL. Fields that differ only in how the portal draws them (a single-line text box versus a text area) share a data type; only the kinds that behave differently keep their own: PARTNER_SELECT picks an Introw partner, QUOTE_SELECTOR an Introw quote, and BATCH_UPLOAD carries no value at all (it is the portal’s bulk-CSV control, so over the API you send one request per submission).
Options. options is present exactly when dataType is DROPDOWN, DROPDOWN_MULTI, or PARTNER_SELECT, and is resolved live: from the CRM picklist behind the field, the pipeline stages of the form’s own CRM automation, the organisation’s synced CRM owners, the partner audience of a partner-select field, or the builder’s preset list. Options limited by the builder are already excluded. Prefer sending value. A label is also accepted and resolved to its value on submission (case-insensitively), so a payload built from human-readable names still lands correctly in the CRM; a value matching no option is passed through untouched rather than rejected, which is what keeps unrestricted picklists working. Send DROPDOWN_MULTI values joined with ;. An empty array means the option set could not be resolved (for example the CRM property has not synced yet), which is a configuration problem to fix in Introw rather than something to work around in the payload.
Fetch this whenever the form may have changed rather than caching it indefinitely: adding a required field, or changing a picklist in the CRM, changes what a valid submission looks like.
Authorizations
Introw API key shown once when the credential is created.
Path Parameters
Identifier of the form, shown in the form's share dialog and in the form URL. Form identifier, shown in the form's share dialog and in the form URL.
1Response
Form schema was resolved.