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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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