POST /v1/terminal/readers/{reader}/collect_inputs

Initiates an input collection flow on a Reader.

Servers

Path parameters

Name Type Required Description
reader String Yes

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/x-www-form-urlencoded"

Request body fields

Name Type Required Description
inputs[] Array Yes

List of inputs to be collected using the Reader

inputs[].required Boolean No
inputs[].selection Object No
inputs[].selection.choices[] Array Yes
inputs[].selection.choices[].id String Yes
inputs[].selection.choices[].text String Yes
inputs[].selection.choices[].style String No

Possible values:

  • "primary"
  • "secondary"
inputs[].type String Yes

Possible values:

  • "numeric"
  • "email"
  • "text"
  • "phone"
  • "signature"
  • "selection"
inputs[].custom_text Object Yes
inputs[].custom_text.skip_button String No
inputs[].custom_text.description String No
inputs[].custom_text.submit_button String No
inputs[].custom_text.title String Yes
inputs[].toggles[] Array No
inputs[].toggles[].default_value String No

Possible values:

  • "disabled"
  • "enabled"
inputs[].toggles[].description String No
inputs[].toggles[].title String No
expand[] Array No

Specifies which fields in the response should be expanded.

metadata Object No

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.