POLICY_EVENT_RECORD
Record a policy event in the policy timeline.
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_EVENT_RECORD",
"payload": {
"policyId": "<UUID of the policy ID>",
"type": "NOTE",
"label": "<Label>",
"description": "<Description>",
"effectiveDate": "2026-03-01"
}
}'
{
"lineId": "<UUID of the product ID>",
"type": "POLICY_EVENT_RECORD",
"payload": {
"policyId": "<UUID of the policy ID>",
"type": "NOTE",
"label": "<Label>",
"description": "<Description>",
"effectiveDate": "2026-03-01"
}
}
Request Fields#
See the shared event envelope. Set type to POLICY_EVENT_RECORD and provide the payload below.
Payload Fields#
| Property | Required | Description |
|---|---|---|
policyId | Yes | Target policy identifier to append the event to. |
type | No | Business type of the policy event. |
label | No | Short label or title for the event. |
description | No | Description or notes for the event. |
effectiveDate | Yes | Date (YYYY-MM-DD) the event is effective on. |
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.