Webhook event types
4 min read Updated February 12, 2026
Event Format
All webhook events follow the same envelope format:
json
{
"id": "evt_abc123",
"type": "screening.completed",
"created": "2026-02-12T14:30:00Z",
"data": { ... },
"environment": "production"
}Available Event Types
### Compliance Events
screening.completed— A restricted party screening has finished processingscreening.match_found— A screening found a potential watchlist match (score ≥ threshold)export_license.decision— An export license determination has been made
### Filing Events
filing.submitted— An AES/EEI filing was submitted to CBPfiling.accepted— Filing accepted; ITN assignedfiling.rejected— Filing rejected with error codesfiling.status_changed— Any filing status transition
### Data Events
data.source_updated— A government data source has been refresheddata.source_stale— A data source has exceeded its freshness threshold
### Account Events
key.created— A new API key was generatedkey.revoked— An API key was revokedsubscription.changed— API vertical subscriptions were modified
Filtering Events
When configuring your webhook endpoint, select only the event types you need. This reduces noise and ensures your endpoint only processes relevant events.
Was this article helpful?