Submit a form
Submits an Introw form (deal registration, lead share, onboarding, feedback, …) server-to-server. The payload is validated against the form’s field definitions and runs the exact same pipeline as a partner filling in the form on the portal: CRM object automations, the form’s acceptance flow, notifications, and timeline events.
Use this to register deals or share leads from your own systems (a partner-facing app, an internal tool, or another platform) without sending anyone to the form itself.
Field ids. fields is keyed by form field id. Field ids are opaque, generated identifiers (for example qkzv8h2m4t6r1yc9pd3sxf70). They are never human-readable names, and they are unique per form. Call GET /api/v1/forms/{formId}/schema for the exact list (every field id, its label, whether it is required, the value shape to send, and the allowed values of every picklist), or read it off the form’s Share → API tab in Introw. Values are validated with the form’s own rules; a payload that violates them (missing required fields, wrong formats) returns 422 with per-field details. Keys that don’t match a form field are ignored.
Picklists. For a DROPDOWN, DROPDOWN_MULTI or PARTNER_SELECT field, send one of the option values the schema lists (join multiple with ;). Option labels are accepted too and resolved to their value case-insensitively, so “Qualified to buy” and qualifiedtobuy both work, and a partner can be named rather than referenced by id. A value matching no option is passed through as sent, so an unrestricted picklist keeps accepting free text.
Partner attribution. Pass partnerId to relate the submission to a specific partner (the same guarantee as the form’s partner-specific share link). It accepts either the Introw partner id or the partner’s CRM external id, so you can key off whichever identifier your own systems already hold; an identifier that matches neither returns 404. With only email, Introw makes a best effort to resolve the partner from the submitter, the same behaviour as the form’s general share link.
Status. Forms without an acceptance flow auto-accept the submission and trigger their automation immediately (AUTO_ACCEPTED). Forms with an acceptance flow return PENDING until a teammate (or the AI acceptance agent) processes the submission.
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.
1Body
Submitted values keyed by form field id. Field ids are opaque, generated identifiers (for example qkzv8h2m4t6r1yc9pd3sxf70), never human-readable names. Fetch them from GET /api/v1/forms/{formId}/schema, which lists every field id with its label, whether it is required, the value shape to send, and the allowed values of every picklist. Values that fail the form's validation rules return 422; keys that don't match a field are ignored.
Email of the person submitting the form, when known. Used to resolve the submitter identity and, together with the form's identification automations, relate the submission to a partner.
^(?!\.)(?!.*\.\.)([A-Za-z0-9_'+\-\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$Partner to relate the submission to. Accepts the Introw partner id or the partner's CRM external id. Returns 404 when it matches neither. When omitted, Introw makes a best effort to resolve the partner from the submitter email.
1CRM objects from the submitting partner's own CRM to link to the submission.
Response
Form was submitted successfully.