Developer API
Add sanctions, PEP and criminal-watchlist checks to onboarding or monitoring through one REST API. Use scoped API keys, submit single or batch searches, and retain structured results for review and audit. Cases that need ownership or relationship research can continue into a deeper KYB or UBO workflow in the platform.
API v1 is live
Endpoints are generally available with API-key auth and per-tier rate limits. Explore every endpoint in the interactive OpenAPI docs at /api/v1/docs.
Create a scoped API key in your dashboard, or mint one programmatically with your account bearer token for server-to-server requests.
curl -X POST https://screenveritai.com/api/v1/keys \
-H "Authorization: Bearer <SUPABASE_JWT>" \
-H "Content-Type: application/json" \
-d '{"name":"server-key","permissions":["search:read","search:write"]}'Submit an entity with the X-API-Key header and choose sanctions_check, adverse_media, full_search, or deep_research_report. The API returns a search id and an estimated time; retrieve the result when processing completes.
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 Ltd","entity_type":"company","search_type":"full_search"}'Send a CSV/XLSX file with name, optional country, and optional search_type. Use one search type per file: sanctions_check, adverse_media, or full_search. Deep Research is per-case only and is not accepted in batch.
curl -X POST https://screenveritai.com/api/v1/batch \
-H "X-API-Key: <YOUR_API_KEY>" \
-F "file=@entities.csv"POST /api/v1/search
Create one Quick Check (sanctions_check), Adverse Media Check (adverse_media), Full Search (full_search), or Deep Research Report (deep_research_report) using search_type. Returns a search id, processing status and an estimated time. Deep Research runs as a durable background job — poll for the result rather than holding the connection open.
Auth: X-API-Key (search:write)
POST /api/v1/batch
Submit CSV/XLSX files for high-volume screening. The optional search_type column defaults to sanctions_check, must be consistent across the file, and does not accept deep_research_report.
Auth: X-API-Key (batch:write)
POST /api/v1/keys
Create and manage API credentials with scoped permissions, tier-aware rate limits, and usage tracking.
Auth: Bearer token (account)
Implementation patterns for API-key auth, async jobs, and audit logs.
ANNEX BConnect API and file-based flows for high-volume operations.
ANNEX CMap API responses into deterministic screening and escalation decisions.
ANNEX DSee the official criminal and wanted-person lists included with sanctions and PEP checks.
Screening requests to /api/v1/search and /api/v1/batch authenticate with an API key sent in the X-API-Key header. Create keys in your dashboard, or programmatically via /api/v1/keys after authenticating with your account bearer token.
Yes. API v1 is live and generally available. Authenticate with an API key, call the search, batch, and key-management endpoints, and explore everything in the interactive OpenAPI docs at /api/v1/docs.
Yes. Keys support permissions such as search:read, search:write, batch:read, and batch:write so you can enforce least-privilege access per integration.
Rate limits are assigned per API tier and enforced per API key — the tier governs request throughput, not billing. Response headers include the limit, remaining quota, and reset timestamps so you can back off cleanly.
Use the interactive documentation at /api/v1/docs for Swagger testing and /api/v1/redoc for reference-style docs. The OpenAPI schema is served at /api/v1/openapi.json.