INTAKE_COMPLETE

User has completed entering information.

Submit this event using Firing an Event. Product configuration and enabled actions determine the workflow behavior. Use identifiers and snapshots from the same environment.

Request payload#

POST https://api.{ENV}.dais.com/ioi/v3/event/fire

curl --location --request POST 'https://api.{ENV}.dais.com/ioi/v3/event/fire' \
--header 'Authorization: Basic <Base64-encoded API key and secret>' \
--header 'Content-Type: application/json' \
--data-raw '{
  "lineId": "<UUID of the product ID>",
  "type": "INTAKE_COMPLETE",
  "payload": {
    "referrer": "<Referrer URL>",
    "intake": {
      "<Business name question ID>": {
        "type": "ANSWER",
        "answer": "<Business name>",
        "qid": "<Business name question ID>"
      },
      "<Employee count question ID>": {
        "type": "ANSWER",
        "answer": "42",
        "qid": "<Employee count question ID>"
      },
      "<State question ID>": {
        "type": "ANSWER",
        "answer": "<State code>",
        "qid": "<State question ID>"
      }
    }
  }
}'

{
  "lineId": "<UUID of the product ID>",
  "type": "INTAKE_COMPLETE",
  "payload": {
    "referrer": "<Referrer URL>",
    "intake": {
      "<Business name question ID>": {
        "type": "ANSWER",
        "answer": "<Business name>",
        "qid": "<Business name question ID>"
      },
      "<Employee count question ID>": {
        "type": "ANSWER",
        "answer": "42",
        "qid": "<Employee count question ID>"
      },
      "<State question ID>": {
        "type": "ANSWER",
        "answer": "<State code>",
        "qid": "<State question ID>"
      }
    }
  }
}

Request Fields#

See the shared event envelope. Set type to INTAKE_COMPLETE and provide the payload below.

Payload Fields#

Property	Required	Description
`referrer`	No	Optional string value to track a referral
`intake`	No	Map of question ID to answer object

Response#

This example illustrates the common trigger response structure. Action counts and metadata depend on the actions that run; action-specific result fields are described where applicable.

{
  "triggerRequestId": "<UUID of the trigger request ID>",
  "executedActionCount": 0,
  "expectedResponseCount": 0,
  "metadata": {}
}

Response Fields#

Property	Description
`triggerRequestId`	UUID identifying this trigger execution.
`executedActionCount`	Number of actions reported as executed.
`expectedResponseCount`	Number of expected action responses.
`metadata`	Action-specific results; may be empty.

See Firing an Event for execution modes and response handling.