Skip to main content
post/form/human_input/{form_token}
Request example
Response
post/form/human_input/{form_token}

Authorization

Authorizationstringheaderrequired#

Every request authenticates with an API key: Authorization: Bearer {API_KEY}. App endpoints take an app API key; knowledge endpoints take a knowledge base API key (Get Started).

Keep keys server-side; never embed them in client code. Requests with a missing or invalid key fail with HTTP 401 (unauthorized).

Path parameters

form_tokenstringrequired#
Access token for the paused form, returned in the human_input_required event from the Run Workflow or Send Chat Message endpoint in streaming mode.

Body

application/json
actionstringrequired#
ID of the action button the recipient selected. Must match one of the id values from the form's user_actions list (returned by Get Human Input Form).
inputsobjectrequired#

Submitted values keyed by each input's output_variable_name. Paragraph and select inputs take a string; a file input takes one file mapping; a file-list input takes an array of file mappings.

A file mapping is {transfer_method: local_file, upload_file_id, type} or {transfer_method: remote_url, url, type}, where type is one of the field's allowed_file_types. For local_file, upload_file_id is the id from Upload File.

Use a consistent user across the run, upload, and submit.

userstringrequired#
End-user identifier, defined by your app and unique within it. Service API and web app user IDs are separate, even when identical. See End User Identity.

Responses

application/json
Form submitted successfully. The response body is an empty object.