sanctions.io · Rate Limits

Sanctions Io Rate Limits

sanctions.io does not publish fixed numeric per-minute request-rate limits for the API. Consumption is governed primarily by plan volume - each plan includes a number of API calls/screenings that renews after twelve months or once consumed, and Enterprise plans start at 25,000+ monthly screenings. The screening endpoint averages roughly 500-600ms response time and supports real-time use cases; batch screening accepts up to 10,000 records per request. The API returns HTTP 429 (Too Many Requests) - for example on the database exporter endpoint when a plan does not permit the operation - and a screenings count endpoint (GET /searches/count) lets accounts track usage against plan volume.

Sanctions Io Rate Limits is the machine-readable rate-limit profile for sanctions.io on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests, screenings, records, words, and characters.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Anti-Money Laundering, AML, Sanctions Screening, Rate Limiting, and Quotas.

6 Limits Throttle: 429
Anti-Money LaunderingAMLSanctions ScreeningRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the API.
Plan Screening Volume account
screenings
per plan (5,000 / 50,000 / 200,000 packages; Enterprise 25,000+ monthly)
Plans renew after twelve months or once included API calls are consumed, whichever comes first.
Batch Screening Size request
records
10000
The batch endpoint accepts up to 10,000 names in a single API request.
Screening Name Length request
words
15
The name parameter accepts a maximum of 15 words.
Identifier Length request
characters
120
The identifier parameter accepts a single identifier of up to 120 characters.
Database Export Access plan
requests
plan-gated
The exporter endpoint requires a specific plan subscription and returns 429/permission errors otherwise.

Policies

Usage Tracking
Track consumed screenings against plan volume with GET /searches/count.
Webhooks over Polling
Register a webhook via the company config endpoint to receive batch-result and monitoring-alert events instead of polling the API.
Webhook Failure Disabling
Webhook endpoints that repeatedly fail delivery are automatically disabled and must be manually re-enabled.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/sanctions-io-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.