On this page

Screening webhooks

Screening event names are list-agnostic. Inspect data.type and the linked screening resource to distinguish sanctions, PEP, adverse media and wallet screening. Internal source records and raw watchlist documents are not included in webhook payloads.

Events

Event	When it fires	Recommended handling
`screening.completed`	A screening run completes.	Persist status and match count.
`screening.match`	A non-clear match needs review.	Open or update review using the screening ID and alert ID.
`screening.insufficient_data`	The customer profile cannot support the check.	Collect the missing customer information before retrying.
`screening.failed`	A screening run cannot complete.	Inspect the public reason code and `retryScheduled`.
`screening.stale`	The profile changed while the check ran.	Wait for or trigger the fresh run.
`screening.adjudicated`	An analyst confirms or clears a match.	Apply the recorded outcome to your review workflow.
`screening.adjudication_overdue`	A match passes its review deadline.	Escalate to the assigned compliance queue.

Complete match example

json

{
  "version": "2026-08-11",
  "id": "evt_screening_match_01",
  "type": "screening.match",
  "createdAt": "2026-08-15T16:20:00.000Z",
  "deliveryId": "del_screening_match_01",
  "data": {
    "screeningId": "scr_01",
    "entityId": "ent_01",
    "subject": {
      "entityId": "ent_01",
      "externalUserId": "customer-123",
      "identityId": "idn_01",
      "type": "individual"
    },
    "type": "SANCTIONS",
    "status": "POTENTIAL_MATCH",
    "assurance": "STANDARD",
    "reasonCode": "name_plus_one",
    "matchCount": 2,
    "alertId": "alt_01",
    "environment": "SANDBOX"
  }
}

Field reference

Field	Type	Nullable	Values and meaning
`screeningId`, `entityId`	string	No	Screening and subject Entity IDs.
`subject`	object	Yes	Customer-safe Entity correlation, including your `externalUserId` when available.
`type`	string	No	`SANCTIONS`, `PEP`, `ADVERSE_MEDIA` or `WALLET`.
`status`	string	No	Current screening state such as `CLEAR`, `POTENTIAL_MATCH`, `INSUFFICIENT_DATA`, `FAILED` or `STALE`.
`assurance`, `reasonCode`	string	Yes	Customer-safe quality level and explanation.
`matchCount`	integer	Yes	Matches in this result.
`alertId`	string	Yes	Review alert opened or reused for a non-clear result.
`outcome`	string	Yes	Analyst outcome on `screening.adjudicated`.
`retryScheduled`	boolean	Yes	Whether a failed or stale check will retry.
`environment`	string	Yes	Environment that produced the result.

Retrieve GET /api/v1/monitoring/screenings/{screeningId} for current match records, attempts and the customer-safe adjudication history. In the dashboard, screening evidence is shown in the customer, risk decision, transaction, or investigation that gives it context. Internal source identity, attempt IDs, profile digests, billing flags, datasets and raw responses are intentionally absent.