Quiltt · Rate Limits

Quiltt Rate Limits

Quiltt enforces rate limits across its surfaces. The most explicitly documented limit is on Session Token issuance, capped per Profile at 10 per hour and 20 per day; revoked tokens are freed and do not count. The GraphQL Data API and REST Admin API also apply per-environment throttling that is not published as fixed numeric values. Clients should cache session tokens (valid ~24 hours) and back off on throttling.

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

It captures 4 rate-limit definitions, measuring tokens and requests.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Fintech, Open Banking, Financial Data, Aggregation, and GraphQL.

4 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
FintechOpen BankingFinancial DataAggregationGraphQLRate LimitingQuotasThrottling

Limits

Session Tokens Per Hour profile
tokens
10
Session tokens issued per Profile per hour. Revoked tokens are freed.
Session Tokens Per Day profile
tokens
20
Session tokens issued per Profile per day. Revoked tokens are freed.
GraphQL Data API environment
requests
see provider documentation
Per-environment throttling on the GraphQL endpoint; values not published.
REST Admin API environment
requests
see provider documentation
Per-environment throttling on Admin endpoints; values not published.

Policies

Token Caching
Cache session tokens client-side (valid ~24 hours) and check expiration before reissuing to avoid the per-Profile issuance limit.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.

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/quiltt-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.