Fragment · Rate Limits

Fragment Dev Rate Limits

Fragment does not publish specific numeric rate limits on its public docs. As a region-scoped GraphQL API used for money movement, callers should expect per-account throttling and should design for idempotent retries: every write mutation carries an idempotency key (ik), so a retried request after a throttle or timeout will not double-post. Specific per-account limits are set by Fragment and are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests and concurrent_writes.

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 Ledger, GraphQL, Rate Limiting, Quotas, and Throttling.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
LedgerGraphQLRate LimitingQuotasThrottling

Limits

Per-Account Request Limit account
requests
see provider documentation
Region-scoped GraphQL endpoint; concrete throttling values are not published.
Write Concurrency ledger
concurrent_writes
see provider documentation
Concurrent postings to a ledger; use idempotency keys so retries are safe.

Policies

Idempotent Retries
Every write mutation (addLedgerEntry, reconcileTx, syncCustomAccounts, syncCustomTxs, createLedger, storeSchema, reverseLedgerEntry) accepts an idempotency key. Retry the same request with the same key to recover from a throttle, timeout, or network error without double-posting.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 / 5xx and honor any Retry-After header.
Short-Lived Tokens
OAuth2 client-credentials access tokens expire in about 1 hour; cache and refresh tokens rather than minting one per request.

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/fragment-dev-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.