This page requires JavaScript to display.

Rate limits

Get started

Per key, per second, with a burst allowance. The check endpoint is sized to be called before every action — that is the point of it, so it is not the one we throttle first.

Scope Limit Burst Note

Headers on every response

Response headers

Sidaxis-RateLimit-Limit: 1000 Sidaxis-RateLimit-Remaining: 947 Sidaxis-RateLimit-Reset: 1 # on 429 only Retry-After: 2

A 429 carries rate_limited . Back off for Retry-After , then retry with the same Idempotency-Key — the replay returns the original response and consumes nothing twice. Exponential backoff with jitter; a tight retry loop is how a burst becomes an outage.

The public check has no account limit GET /receipts/{id}/verify takes no key, so there is no account to meter. A fair-use ceiling applies per IP to keep it available; a throttled IP never means a throttled account. Independent verification that we could rate-limit per customer would not be independent.

Raising a limit

Limits are per key, so splitting traffic across keys per tool is usually the answer before asking us. Sandbox limits are lower on purpose — do not size a launch against them. For a genuine step change, send the expected peak per second and the window, and we raise it on the account.

See also Idempotency → Errors & refusals →

ScopeLimitBurstNote
POST /mandates/{id}/check1,000 req/s per key2,000The hot path. Built to be called before every action.
POST /identity/recognitions200 req/s per key400Free at any volume; the limit is throughput, not cost.
POST /identity/claims50 req/s per key100Claims are once per person, so bursts are rare and suspicious.
POST /sessions100 req/s per key200One session per person per flow. Reuse nothing.
All GET endpoints300 req/s per key600Reads are never billed, but they are still metered.
Every key on the workspace3,000 req/s per workspace5,000The account ceiling. Splitting across keys raises per-key headroom, not this.
GET /receipts/{id}/verifyNo account limitFair use per IPPublic and free. There is no account to limit; abusive IPs are throttled, never accounts.
Unpacking...