Overview
TheAGENT_REGULATORY_ACTION_UPDATED webhook is triggered when the daily NIPR PDB-alerts pass reports that a regulatory action already on file against one of your producers has been amended.
Regulators revise filings routinely, and the revision is often the part that matters. The case this event was built for: an action first recorded in July came back from a later pass with its disposition escalated to Cease And Desist, Cease And Desist From All Insurance Activity. The action was already on file, so no new-action event fired, and the carrier heard nothing about the escalation.
Agent Regulatory Action Added tells you an action exists. This event tells you what it now says.
Webhook type: AGENT_REGULATORY_ACTION_UPDATED
Triggers
This webhook fires when the daily NIPR PDB-alerts pass changes any of the nine amendable fields on an action already stored:originOfAction, reasonForAction, disposition, dateOfAction, effectiveDate, enterDate, fileRef, penaltyFineForfeitureInUSD or lengthOfOrderInDays.
A field being cleared counts as a change, and arrives with the field listed in changedFields and null at the top level.
This webhook is sent immediately, with no debouncing, and there is one delivery per amended action.
What does not fire this event
A pass that changes nothing delivers nothing
The daily NIPR pass re-reads every action it already holds for you and compares it against what we have stored. When nothing has changed, nothing is written and nothing is sent. You receive an event only when one of the nine amendable fields genuinely changed value. So the volume of this event tracks real regulator activity, not our polling schedule. Deliveries are rare and bursty rather than daily.Payload Example
A disposition escalating from a suspension to a cease-and-desist:Payload Fields
Every field Agent Regulatory Action Added carries, in its current state after the amendment, plus the two diff fields at the end.previousValues has three states and they mean different things.- The whole object is
null: we could not read the prior state of the action. The current values are still correct. Re-read from the API if you need the history. - A key is absent: that field was not part of this amendment.
- A key is
null: the field had no value before, so this amendment populated it.
previousValues and null at the top level.
Never read a null inside previousValues as “cleared”, it is the opposite.The entity fields behave exactly as on the Added event.
agentId, downstreamEntityAssociationId,
branchName and legalName come from one best-effort lookup against your association with the producer’s agency.
Either all of them arrive or none of them do, and absent means “we could not resolve this” rather than anything about
the data.When a producer works under more than one of your agencies, the agency fields name an arbitrary one of those
relationships. agentId is exact; match on it.Deduplication
Key onactionId + npn + stateCode, the same key the Added event uses, so an amendment updates the record you
already hold rather than creating a second one.
The whole action is delivered rather than the diff alone, which means you can apply this event as a wholesale
overwrite of your copy and ignore changedFields entirely if you have no use for it.
No fan-out across carriers
If the same producer appears on more than one carrier’s book, each carrier holds their own copy of the action and each receives exactly one delivery per amendment, carrying their owndownstreamEntityAssociationId.