Sift · Rate Limits

Sift Rate Limits

Sift does not publish fixed numeric public rate limits for its REST APIs. Throughput is governed by your commercial agreement (contracted event / request volume) rather than a documented per-minute request cap. Sift's client libraries and documentation indicate that requests may be throttled under load, and clients should handle 429 (Too Many Requests) and 5xx responses with exponential backoff and retries. The synchronous Score path (Events API with return_score=true, or the Score API) is the most latency- and volume-sensitive surface and should be batched or rate-managed on the client side.

Sift Rate Limits is the machine-readable rate-limit profile for Sift on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and events.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Fraud Detection, Trust and Safety, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Fraud DetectionTrust and SafetyRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented; governed by contract volume.
Synchronous Scoring account
requests
not published
Events API with return_score=true and the Score API are latency-sensitive; manage concurrency client-side.
Contracted Event Volume account
events
per agreement
Monthly event / transaction / user assessment volume is set by the commercial agreement.

Policies

Backoff Strategy
On 429 or 5xx responses, retry with exponential backoff and jitter, as implemented in Sift's official client libraries.
Idempotency
Events carry a client-supplied identity; resending the same event is used to correct or update prior data rather than being rejected as a duplicate.
Client-Side Throttling
High-volume ingestion should be batched and rate-managed by the client, since Sift does not publish a hard public QPS cap.

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/sift-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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