Data API

Data API Documentation

Developer documentation for the Sanctions Atlas Data API: read-only programmatic access to the published sanctions dataset, covering canonical entities, authority source records, programs, relationships, and the published change log.

The guide covers authentication with API keys, the entity and record model (including how merged ids keep resolving), cursor pagination, error codes, per-plan rate limits and quotas, dataset freshness, and per-authority coverage with attribution requirements.

Sanctions Atlas provides structured sanctions data infrastructure over official published records. It is not a screening or decision engine; matching and compliance determinations remain with the customer's systems and processes. Coverage is published authority by authority, every record carries the issuing authority and its required attribution, and every response states the dataset version that answered it, so any value can be verified against the issuing authority.

• Base URL: https://api.sanctionsatlas.com/v1
• Authentication: Authorization: Bearer $SANCTIONS_ATLAS_API_KEY (keys are created at /data-api and shown once)
• First request: curl "https://api.sanctionsatlas.com/v1/search?q=example+shipping+company" -H "Authorization: Bearer $SANCTIONS_ATLAS_API_KEY"
• Next request: Take data[0].id from the response and call GET /v1/entities/{id} for the full entity document.
• Machine-readable contract: https://api.sanctionsatlas.com/v1/openapi.json (OpenAPI 3.1, no API key required)
• Plain-text index: https://sanctionsatlas.com/llms.txt
• Rate limits and quotas: API Standard: 10,000 metered requests a month per account, 60 requests a minute per key. API Professional: 100,000 a month per account, 300 a minute per key. The monthly quota is shared by every key on an account; the per-minute rate is per key.
• Staying in sync: Poll GET /v1/changes with since on published_at and dedupe on change_id. It is a polling change log, not a stream.