Put sanctions screening inside the workflow that needs it
Use the API for sanctions, PEP and criminal-watchlist screening in onboarding, payments, procurement, or monitoring. Full Search can add adverse-media context; cases that require ownership or relationship research continue into the platform's deeper KYB and UBO workflow.
The request
p. 01 / 09One POST call, then your poll loop.
Entity name, type, country, screening type. The call returns 202 with a search_id and an ETA, and the agent works in the background — you poll for the result rather than hold the connection open.
entity_nameRequired, 1-500 characters. Alias-aware matchingentity_type"person", "company" or "any" (default "any")countryOptional jurisdiction hint that sharpens identity resolutionsearch_type"sanctions_check", "adverse_media" or "full_search"The response
p. 02 / 09Structured JSON. Findings, not a score.
One field per sanctions source, plus criminal watchlists and PEP. Each finding is markdown carrying the status line, the matched entity, the authority and an evidence URL — there is no numeric score and no risk tier, because a number hides the line an auditor asks to see.
"ofac_sanctions"One markdown field per jurisdiction; read the *Status:* line"sanctions_sources"source_id, title, authority, details, hit_count per source"criminal_watchlists"Markdown when matched, null when nothing matched"pep"Markdown when matched, null when nothing matched"news_summary"Adverse-media report on adverse_media and full_search"status"completed when done; error_* on failureAPI reference
p. 03 / 09Three calls cover a screening integration: queue it, poll it, or hand over a file.
/api/v1/searchQueue a screening run. Returns immediately with a search_id; the work happens in the background.
Request
Response
202 AcceptedIntegration patterns
p. 04 / 09The API sits between data entry and decision — wherever you need a risk signal.
Build in-house vs. integrate ScreenVeritAI
p. 05 / 09- Build in-house
- 6-12 months to source lists, build matching, handle edge cases
- ScreenVeritAI API
- Days to integrate — production-ready from first API call
- Build in-house
- Manual ingestion of each list format; ongoing schema maintenance
- ScreenVeritAI API
- Every major source, maintained and updated continuously
- Build in-house
- Custom fuzzy matching requires NLP expertise and constant tuning
- ScreenVeritAI API
- AI with fuzzy matching, transliteration, alias resolution, phonetic algorithms
- Build in-house
- Separate vendors, separate integrations, separate budgets
- ScreenVeritAI API
- Sanctions, PEP and criminal watchlists in one response; adverse media on a Full Search
- Build in-house
- Dedicated team for list updates, schema changes, false-positive tuning
- ScreenVeritAI API
- Fully managed — updates, improvements, and infrastructure handled for you
- Build in-house
- Build your own logging, evidence, and retention infrastructure
- ScreenVeritAI API
- Timestamped evidence bundles with source references included
Four steps to embedded compliance
p. 06 / 09Get 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 from your onboarding, payment, or CRM workflow. Send entity_name, entity_type and country; you get back a search_id and an estimated_time_seconds.
Process results
Poll GET /api/v1/search/{search_id} until status is completed. The JSON carries one markdown finding per sanctions source, plus criminal_watchlists, pep and, on a Full Search, news_summary.
Re-screen on a cadence
The v1 API has no webhooks, so schedule the repeat call yourself, or turn on monitoring in the platform for in-app alerts when a listing changes.
Get started in minutes
p. 07 / 09A single API call returns a complete screening result.
curl -X POST https://screenveritai.com/api/v1/search \
-H 'X-API-Key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"entity_name": "Acme Trading LLC", "country": "AE", "search_type": "sanctions_check"}'
# 202 Accepted
# { "search_id": "SEARCH_ID", "status": "processing", "estimated_time_seconds": 15 }curl https://screenveritai.com/api/v1/search/SEARCH_ID \
-H 'X-API-Key: YOUR_API_KEY'
# 200 OK
# { "id": "SEARCH_ID", "status": "completed",
# "ofac_sanctions": "## OFAC Sanctions Findings ... *No relevant listing found* ...",
# "criminal_watchlists": null, "pep": null }API performance
p. 08 / 09€0.39
Quick Check per call, no platform fee
202
HTTP status when a search is accepted; you then poll the result
EU
Hosted in Finland; data at rest stays in the EU
API integration FAQ
p. 09 / 0901How do I authenticate API requests?
02Is the API synchronous or asynchronous?
03What response format does the API return?
04What rate limits apply?
05Can I screen entities in batch via the API?
06How do I set up ongoing monitoring via the API?
07What compliance data is included in each screening result?
08How long does a screening take?
- 01FATF Guidance on Digital Identity and Customer Due Diligence
Financial Action Task Force
- 02Regulatory Technology for AML/CFT Compliance
Bank for International Settlements — FSI Insights
- 03OFAC Compliance Commitments Framework
U.S. Department of the Treasury
- 04EU Anti-Money Laundering Authority (AMLA) Regulation
Official Journal of the European Union
Sanctions Screening
Screen entities across every major source with fuzzy matching and enforcement-grade evidence.
Customer Screening & Due Diligence
Map ownership, PEP exposure, adverse media, and sanctions signals for full counterparty risk profiles.
Batch Screening
Upload CSV or XLSX files and verify hundreds of customers, suppliers, or vendors in one job.
Sanctions List Coverage
See every sanctions list, PEP database, and jurisdiction ScreenVeritAI covers.
End of API specification.