Screening inside your own onboarding flow

A documented REST API, signed webhooks and official SDKs. Sub-100 ms response and a contractual 99.9% uptime.

Get a sandbox key

87 ms

Median /v1/screen

99.9%

Contractual SLA

Official SDKs

Performance and accuracy figures shown on this site are measured in controlled test environments on representative datasets. Real results vary with data quality, list configuration and volume. The only binding commitments are those stated in the service agreement.

POST /v1/screen200 · 87 ms

{
  "screening_id": "scr_8839210045x",
  "name": "Nordwind Handels GmbH",
  "entity_type": "organization",
  "score": 0.94,
  "severity": "critical",
  "matches": [
    { "list": "EU_CFSP", "reference": "2023/1214#118", "confidence": 0.41 }
  ],
  "case_id": "ALT-40921",
  "screened_at": "2026-08-16T14:32:07Z"
}

Every response carries a case_id — the file already exists

02API reference

Section 02 · API reference

Four endpoints cover the whole cycle

OAuth 2.0Bearer tokenHMAC webhooks

POST/v1/screenScreen an entity against sanctions, PEP, and adverse media lists.

Requirement	Parameter	Type	Description
required	name	string	Entity name to screen
required	entity_type	string	individual · organization
optional	lists	array	sanctions · pep · adverse_media
optional	birth_date	string	Date of birth (YYYY-MM-DD)
optional	country	string	ISO 3166-1 alpha-2

GET/v1/screen/{screening_id}Retrieve the results of a previous screening.

Requirement	Parameter	Type	Description
required	screening_id	string	Unique screening identifier

POST/v1/batchSubmit a batch of entities for bulk screening.

Requirement	Parameter	Type	Description
required	entities	array	Array of entity objects
optional	callback_url	string	Webhook for completion notice

POST/v1/monitorAdd an entity to continuous monitoring.

Requirement	Parameter	Type	Description
required	entity_id	string	Your internal identifier
required	name	string	Entity name
optional	alert_email	string	Email for change alerts

03Quick start

Section 03 · Quick start

From key to first match, in two calls

The sandbox returns real matches against a fixed dataset, so you can write your assertions before there is a contract.

Screen an entity · cURLshell

curl -X POST https://api.xpectra.io/v1/screen \
  -H "Authorization: Bearer $XPECTRA_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Nordwind Handels GmbH",
    "entity_type": "organization",
    "lists": ["sanctions", "pep", "adverse_media"],
    "country": "DE"
  }'

Webhook payload · monitoringPOST yours

{
  "event": "monitor.match_found",
  "entity_id": "cust_10421",
  "list": "OFAC_SDN",
  "severity": "critical",
  "case_id": "ALT-41077",
  "signature": "sha256=9f2c…",
  "occurred_at": "2026-08-16T14:32:07Z"
}

Verify signature with HMAC-SHA256 before trusting the payload

Pythonv2.1.0

pip install xpectra

Node.jsv3.0.2

npm install @xpectra/sdk

Rubyv1.5.0

gem install xpectra

04Library

Section 04 · Library

Everything you will need

Each resource states its status and when it was last updated, so you know whether to trust it.