Get regulatory actions for a specific NPN
Returns all regulatory actions associated with a specific NPN. If you’re not already subscribed, this request will automatically subscribe you to the NPN.
Query Parameters
comma separated list of states abbreviations (must be 2 characters) - this will filter on the forState field
Example:MO, CA, CO
limits results to those that have an updated date equivalent to or after to the date provided (YYYY-MM-DD) - this will filter on the updatedAt field
Example:2024-10-15
specifiy whether or not deleted records should be included in the response - this will filter on the niprDeleted field
Default:true
the number of objects on the page (min = 1 / max = 1,000)
Default:250
>= 1<= 1000
Token for fetching the next page of results
Path Parameters
National Producer Number (npn) of the data to return
Example:123456789
Response
application/hal+json
Response
Success
Show Child Parameters
Show Child Parameters
Get regulatory actions by ID
Retrieves a single regulatory actions record using its unique regulatory actions ID.
Path Parameters
Unique regulatory actions ID
Response
application/hal+json
Response
Success
RegulatoryActionsV1
Common regulatory actions fields shared across versions.
Unique identifier for the regulatory actions.
Example:1234567
National Producer Number associated with the regulatory actions.
Example:18551108
Example:ae51f10b-8b5e-40ba-98a9-8f860392b344
State where the regulatory action applies.
>= 2 characters<= 2 characters
Example:AL
Identification of the regulatory action.
Example:13537078
The date the regulatory action occurred.
Example:2017-07-10
The date the regulatory action is effective
Example:2017-07-10
The date the regulatory action was entered in the jurisdiction system.
Example:2018-02-08
File reference identifier for the regulatory action, as reported by the jurisdiction. Format varies by
state.
Example:123
Date of the creation of this record in AgentSync.
Example:2021-04-04
Date of the most recent update to this record in AgentSync.
Example:2024-12-02
Amount in USD of fine, if applicable.
Example:150
The sanction period.
Example:30
All regulatory actions should have three associated child objects - disposition, origin, and reason
Show Child Parameters
Indicates if the regulatory actions was marked deleted by NIPR.
Show Child Parameters
Get regulatory action values by ID
Retrieves a single regulatory action value record using its unique regulatory action value ID.
Path Parameters
Unique regulatory action value ID
Response
application/hal+json
Response
Success
RegulatoryActionValuesV1
All regulatory actions should have three associated child objects - disposition, origin, and reason
Unique identifier for the regulatory action value.
Example:123
Unique identifier for the related regulatory action.
Example:1234567
Example:ae51f10b-8b5e-40ba-98a9-8f860392b344
One of the following values is expected per object - REASON, ORIGIN, DISPOSITION
Allowed values:REASONORIGINDISPOSITION
Example:DISPOSITION
Description of the related regulatory action
Example:Cease And Desist
Date of the creation of this record in AgentSync.
Example:2021-03-23
Date of the most recent update to this record in AgentSync
Example:2024-04-16
Show Child Parameters
Example:true
Webhook Events
Outbound events delivered to your configured endpoint when new compliance data is available or your monitored population changes.
producerSyncUpdatesAvailable
WEBHOOKFires once per day, after AgentSync has finished processing NIPR’s refresh
across your entire monitored population.
This is a batch-complete signal, not a per-producer one. There is no event for an
individual NPN, and the payload carries only a runDate — no NPN — because the
event means “every producer you monitor has been processed”, not “this producer
changed”. NIPR publishes once daily, so this is the cadence at which compliance
data can change at all.
Use data.runDate as the value for the updatedSince parameter to fetch just the
records that changed.
Body
application/json
Body
UpdatesAvailableWebhookEvent
Fields common to every ProducerSync webhook event.
Unique identifier for this event, a TypeID with the whe_ prefix. Repeated on retries — use it to deduplicate.
Example:whe_01m0a149wzf6sb9ap9y8tafwe1
The specific event type.
UTC time the event was generated. Fractional-second precision is not fixed - parse with a tolerant RFC 3339 parser rather than a fixed-millisecond format.
Example:2026-08-18T08:52:09.2471298Z
Show Child Parameters
Response
2XX
Response
Customer endpoint acknowledged the event.