Inbound Data

Accepts external inbound data and routes it into the DAIS platform pipeline. This endpoint is used for carrier or third-party systems to push data back into an active workflow — for example, returning a rating result or decision to a pending request.

Endpoint#

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

Returns 204 No Content on success.

Headers#

Header	Value	Required
`Content-Type`	`application/json`	Yes
`Authorization`	`Bearer <Access token>` or `Basic <Base64-encoded API key and secret>`	Yes
`x-jwt-assertion`	`<ID token>`	With token authentication

See Authentication for the headers to use with each authentication method.

Request Body#

curl --location --request POST 'https://api.{ENV}.dais.com/ioi/v3/inbound' \
--header 'Authorization: Basic <Base64-encoded API key and secret>' \
--header 'Content-Type: application/json' \
--data-raw '{
  "requestId": "<UUID of the request ID>",
  "payload": {
    "status": "APPROVED",
    "premium": 4200.0
  }
}'

{
  "requestId": "<UUID of the request ID>",
  "payload": {
    "status": "APPROVED",
    "premium": 4200.0
  }
}

Request Fields#

Property	Required	Description
`requestId`	Yes	UUID of the originating request this response corresponds to.
`payload`	Yes	Non-empty JSON object containing the external system's response. Its fields depend on the integration.

Notes#

Use the requestId associated with the originating workflow in the same environment. The public API forwards the response to the action service, which resolves that request and processes the payload.
The example payload is illustrative. Use the response fields expected by your integration; status and premium are not universal inbound fields.

Response#

Returns 204 No Content. No response body is returned on success.