Skip to main content
Webhooks belong to the Carrier & MGA API. This event fires about an agency you appoint, and only a credential on that surface (carrier, MGA or wholesaler) can subscribe to it.

Overview

The DOWNSTREAM_ENTITY_COMPLIANCE_STATUS_CHANGE webhook is triggered when a downstream entity’s (agency) compliance status changes for any product/state combination. Webhook type: DOWNSTREAM_ENTITY_COMPLIANCE_STATUS_CHANGE

Triggers

This webhook fires when any of the following occur for a downstream entity:
  • Agency license is created, updated, or expires
  • Agency appointment status changes
  • Compliance requirements for a product/state combination are updated
  • PDB (Producer Database) alerts from NIPR affect license or appointment data
This webhook is debounced with a 1-minute sliding window. After the last change in a sequence, Turris waits 1 minute before sending a consolidated webhook. A maximum cap of 30 minutes ensures delivery even during continuous activity.

Payload Example

Field Reference

Entity Fields (each element in payload)

Product Fields (each element in products)

State Fields (each element in states)

Status Object Fields (licenseStatus and appointmentStatus)

When a state is removed from a product’s compliance requirements, licenseStatus and appointmentStatus will both have statusName: "STATE_REMOVED".
appointmentStatus.statusName: "Appointment on Binding" is not an error state. Some states regulate appointments just-in-time: the appointment is filed once business is actually bound, rather than before the agency or agent is authorized to sell. A state in that regime reports this status, and complianceStatus for it is COMPLIANT.We do not receive binding dates, so we do not assert a breach we cannot evidence. If you branch on statusName, treat this value as passing. A comparison against "Not Appointed" will stop matching these states.

Batching

Because this webhook is debounced, a single delivery may contain multiple downstream entities in the payload array, and each entity may have multiple products and states that changed. Design your handler to iterate over the full payload.