VOID_CANCEL_RENEWAL
Void Cancel policy renewal
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": "VOID_CANCEL_RENEWAL",
"payload": {
"clientId": "<UUID of the client ID>",
"quoteId": "<UUID of the quote request ID>",
"policyId": "<UUID of the policy ID>",
"documents": [],
"configId": "<UUID of the configuration ID>",
"label": "<Label>",
"backofficeIntake": {
"reason": {
"type": "ANSWER",
"answer": "<Answer for this question>"
},
"voidDate": {
"type": "ANSWER",
"answer": "2026-11-01"
}
}
}
}'
{
"lineId": "<UUID of the product ID>",
"type": "VOID_CANCEL_RENEWAL",
"payload": {
"clientId": "<UUID of the client ID>",
"quoteId": "<UUID of the quote request ID>",
"policyId": "<UUID of the policy ID>",
"documents": [],
"configId": "<UUID of the configuration ID>",
"label": "<Label>",
"backofficeIntake": {
"reason": {
"type": "ANSWER",
"answer": "<Answer for this question>"
},
"voidDate": {
"type": "ANSWER",
"answer": "2026-11-01"
}
}
}
}
Request Fields#
See the shared event envelope. Set type to VOID_CANCEL_RENEWAL and provide the payload below.
Payload Fields#
Required fields include the inputs used by this event's built-in action. Configured actions can require additional data.
| Property | Required | Description |
|---|---|---|
clientId | No | UUID of the client who owns the policy identified by policyId. |
quoteId | No | UUID of the original quote associated with the policy identified by policyId. |
policyId | Yes | UUID of the policy whose renewal cancellation is being voided. |
documents | No | List of documents related to the event. |
configId | Yes | UUID of the configuration associated with the cancellation. |
label | No | Optional label describing the void action. |
backofficeIntake | No | Map of backoffice form fields to values. |
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.