POLICY_DOCUMENTS_UPLOADED
Document(s) for a policy added.
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": "POLICY_DOCUMENTS_UPLOADED",
"payload": {
"clientId": "<UUID of the client ID>",
"policyId": "<UUID of the policy ID>",
"documents": [
{
"name": "<Document name>",
"extension": "pdf",
"contentId": "<UUID of the document content ID>",
"url": "<Document URL>"
},
{
"name": "<Document name>",
"extension": "pdf",
"contentId": "<UUID of the document content ID>",
"url": "<Document URL>"
}
]
}
}'
{
"lineId": "<UUID of the product ID>",
"type": "POLICY_DOCUMENTS_UPLOADED",
"payload": {
"clientId": "<UUID of the client ID>",
"policyId": "<UUID of the policy ID>",
"documents": [
{
"name": "<Document name>",
"extension": "pdf",
"contentId": "<UUID of the document content ID>",
"url": "<Document URL>"
},
{
"name": "<Document name>",
"extension": "pdf",
"contentId": "<UUID of the document content ID>",
"url": "<Document URL>"
}
]
}
}
Request Fields#
See the shared event envelope. Set type to POLICY_DOCUMENTS_UPLOADED and provide the payload below.
Payload Fields#
| Property | Required | Description |
|---|---|---|
clientId | No | Client identifier associated with the policy and uploaded documents. |
policyId | Yes | Target policy to which the documents were uploaded. |
documents[] | No | Array of saved document records attached to the policy. |
documents[].name | Yes | Original file name stored with the document. |
documents[].extension | Yes | File extension (e.g., pdf, png). |
documents[].contentId | Yes | UUID of the CMS content; required for each supplied document. |
documents[].url | Yes | Nonblank URL to the stored document. |
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.