# Developer API

Why copy-paste names between systems when one API call does it all?

Embed company verification, ownership mapping, PEP checks, adverse media, and sanctions signals directly into your existing workflows.

Get API key View pricing

// The request

One POST call. That's your entire integration.

Entity name, country, screening profile. Send it. The AI agent takes it from there — no orchestration logic on your end.

nameEntity name, alias-aware

countryISO 3166-1 alpha-2 country code

profile"sanctions_check" or "deep_research"

POST /v1/screenbash

1curl -X POST https://api.screenveritai.com/v1/screen \

2 -H 'Authorization: Bearer YOUR_API_KEY' \

3 -H 'Content-Type: application/json' \

4 -d '{

5 "name": "Acme Trading LLC",

6 "country": "AE",

7 "profile": "deep_research"

8 }'

POST /api/v1/screen — response200 OK

2"entity": "Acme Trading LLC",

3"request_id": "srv_a8f3c1d9",

4"processed_at": "2026-03-26T09:14:02Z",

5"sanctions": {

6"status": "clear",

7"lists_checked": 10,

8"matches": []

9},

10"pep": {

11"status": "match",

12"details": "Board member linked to PEP (gov. minister spouse)"

13},

14"adverse_media": {

15"hits": 3,

16"languages": ["en", "ar", "ko"],

17"highest_severity": "medium"

18},

19"ubo": {

20"layers_traced": 3,

21"flagged": true,

22"reason": "UBO connected to sanctioned entity"

23},

24"risk_tier": "enhanced_due_diligence"

25}

Clear / pass

Match / flagged

Hits / warnings

Counts / metadata

// The response

Structured JSON. Every risk vector. Color-coded.

Sanctions status, PEP matches, adverse media hits, UBO flags, and risk tier — all in one response, ready for your decision engine.

"sanctions"Direct list match status + count

"pep"PEP match + relationship detail

"adverse_media"Hit count, languages, severity

"ubo"Layers traced + flagged indicator

"risk_tier"Normalized risk classification

// Endpoints

API Reference

Three endpoints cover all screening workflows.

POST

/v1/screen

Submit an entity for sanctions, PEP, adverse media, and UBO screening.

Request

curl -X POST https://api.screenveritai.com/v1/screen \

-H 'Authorization: Bearer {API_KEY}' \

-d '{"name": "Acme LLC", "country": "AE", "profile": "deep_research"}'

Response

200 OK

{ "request_id": "srv_a8f3c1d9", "status": "queued",

"estimated_seconds": 30, "poll_url": "/v1/result/srv_a8f3c1d9" }

// Integration patterns

Drop into your existing workflow

The API sits between data entry and decision — wherever you need a risk signal.

Customer onboarding

Customer signupPOST /v1/screenDecision engineApprove / reject

Payment processing

Transaction initGET /v1/checkScreen counterpartyRelease / hold

CRM re-trigger

Record updatedWebhook firesPOST /v1/screenAlert if changed

// Build vs buy

Build in-house vs. integrate ScreenVeritAI

Aspect	Build in-house	ScreenVeritAI API
Time to production	6-12 months to source lists, build matching, handle edge cases	Days to integrate — production-ready from first API call
Sanctions list coverage	Manual ingestion of each list format; ongoing schema maintenance	10+ regimes maintained and updated continuously
Matching accuracy	Custom fuzzy matching requires NLP expertise and constant tuning	AI with fuzzy matching, transliteration, alias resolution, phonetic algorithms
PEP and adverse media	Separate vendors, separate integrations, separate budgets	PEP, adverse media, and UBO data in the same API response
Ongoing maintenance	Dedicated team for list updates, schema changes, false-positive tuning	Fully managed — updates, improvements, and infrastructure handled for you
Audit trail	Build your own logging, evidence, and retention infrastructure	Timestamped evidence bundles with source references included

// How it works

Four steps to embedded compliance

Get your API key

Create a scoped key from your dashboard with least-privilege permissions: search:read, search:write, batch:read, batch:write.

Integrate the endpoint

One POST call to your onboarding, payment, or CRM workflow — send entity name, type, and country, get a job ID back.

Process results

Poll the results endpoint or receive a webhook callback with structured JSON — company context, ownership, PEP, adverse media, sanctions signals, and risk scores.

Monitor and alert

Configure ongoing monitoring — the API sends alerts when sanctions lists update or new adverse media surfaces.

// Quickstart examples

Get started in minutes

A single API call returns a complete screening result.

Screen an entitybash

bash

curl -X POST https://api.screenveritai.com/v1/screen \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"name": "Acme Trading LLC", "country": "AE"}'

Check resultbash

bash

curl https://api.screenveritai.com/v1/results/RESULT_ID \
  -H 'Authorization: Bearer YOUR_API_KEY'

API performance

10+

Global sanctions regimes screened per API call

<2 min

Average response time for a full screening with deep research

99.9%

API uptime SLA for production integrations

// FAQ

API integration FAQ

#How do I authenticate API requests?

API key in the Authorization header. Keys are created from your dashboard with scoped permissions.

#Is the API synchronous or asynchronous?

Asynchronous. Submit a request, get a job ID, retrieve results by polling or webhook. Your pipeline never blocks.

#What response format does the API return?

Structured JSON with sanctions matches, PEP flags, adverse media, confidence scores, source references, and risk-tier classification.

#What rate limits apply?

Assigned by subscription tier per API key. Response headers include remaining quota and reset timestamp.

#Can I screen entities in batch via the API?

Yes. The batch endpoint accepts CSV or XLSX with up to 100 rows per request, results retrievable per row or as a complete export.

#How do I set up ongoing monitoring via the API?

Configure monitoring after initial screening. When lists update or new adverse media surfaces, the API sends a webhook to your endpoint.

#What compliance data is included in each screening result?

Sanctions matches across 10+ regimes, PEP status with family connections, adverse media with multilingual citations, UBO data, risk tier, and timestamped evidence bundle.

#How long does a screening take?

Standard sanctions check: seconds. Deep research with adverse media and ownership mapping: under two minutes.

API terminology

REST API

Web API using standard HTTP methods — compatible with any language or framework that can make HTTP requests.

Webhook

Server-to-server HTTP callback triggered when a screening completes or monitoring detects a change.

Async processing

The API accepts a job immediately and processes it in the background — retrieve results via polling or webhook.

API key

Secret token for authenticating API requests, scoped with specific permissions for least-privilege access.

Rate limiting

Restricts API requests per time window by subscription tier — remaining quota and reset timestamps in response headers.

Structured response

Machine-readable JSON with consistent field names and types, enabling automated parsing and decision logic.

/* Industry sources */

[1]
FATF Guidance on Digital Identity and Customer Due Diligence
Financial Action Task Force
[2]
Regulatory Technology for AML/CFT Compliance
Bank for International Settlements — FSI Insights
[3]
OFAC Compliance Commitments Framework
U.S. Department of the Treasury
[4]
EU Anti-Money Laundering Authority (AMLA) Regulation
Official Journal of the European Union

Why copy-paste names between systems when one API call does it all?

One POST call. That's your entire integration.

Structured JSON. Every risk vector. Color-coded.

API Reference

Drop into your existing workflow

Build in-house vs. integrate ScreenVeritAI

Four steps to embedded compliance

Get started in minutes

API performance

API integration FAQ

API terminology

/* Industry sources */

// Explore more

Sanctions Screening

Customer Screening & Due Diligence

Batch Screening

Sanctions List Coverage

Tosaigh ag scagadh i nóiméid.