QUODD · Rate Limits

Quodd Rate Limits

QUODD does not publish fixed numeric API rate limits openly. Access is token-authenticated (a 24-hour token per trial or firm user) and governed by the entitlements in each customer's agreement - which datasets, asset classes, and exchanges are licensed, and whether data is real-time, delayed, or historical - rather than by a published per-minute request cap. Batch snapshot endpoints let callers retrieve many tickers per request to reduce call volume; Cloud Streaming pushes only changing quote/trade fields instead of requiring repeated polling. Concrete quotas are set per contract.

Quodd Rate Limits is the machine-readable rate-limit profile for QUODD on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, hours, tickers, and datasets.

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

Tagged areas include Market Data, Real-Time Data, Financial Data, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Market DataReal-Time DataFinancial DataRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented; governed by the commercial agreement.
Access Token Lifetime token
hours
24
Tokens expire 24 hours after generation and must be regenerated.
Batch Snap Size request
tickers
per contract
Batch Snaps and Batch Options Snaps accept multiple tickers per request; effective size is governed by the agreement.
Dataset Entitlements account
datasets
per contract
Access to real-time, delayed, historical, and reference datasets and specific exchanges is set by entitlements.

Policies

Token Rotation
Clients must regenerate the 24-hour token before expiry and handle 401 responses by re-authenticating.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Prefer Streaming for Live Data
For continuously changing data, use Cloud Streaming rather than repeatedly polling the REST snapshot endpoints.

Sources