Limites et fraîcheur des données

Consultez les quotas de chaque offre ainsi que le fonctionnement du cache et des en-têtes HTTP.

Limites de débit et quotas

Each API key has a per-minute request limit. Going over returns 429 with a Retry-After header suggesting how many seconds to wait.
Some plans have a daily request limit, counted by UTC date and reset at 00:00 UTC.
Every response includes X-RateLimit-Limit (the per-minute limit) and X-RateLimit-Remaining (requests left).
The WebSocket handshake also counts as a request.

Fraîcheur des données

For stability and rate limiting, market data is cached, so it can lag the source slightly. Real-time quotes, ticks and order book are refreshed by the gateway within the upstream quota: as fast as every 3 seconds, and longer when many symbols are requested at once. Use the X-Data-Age header on each response (data age in seconds). The table below gives the cache time for everything else; X-Proxy-TTL shows the actual value in seconds.

Data	Default cache time / refresh interval
Real-time quotes, ticks, order book	As fast as 3 seconds (refreshed by the gateway)
Minute candles (including the current one)	30 seconds
Day, week and month candles (including the current one)	5 minutes
Historical candles with the `et` parameter	1 hour
Symbol list, holidays, basic info	24 hours
Market status	30 seconds

En-têtes HTTP de cache

X-Proxy-Cache	Meaning
`HIT` / `L2-HIT`	Served from cache
`MISS`	Fetched from the upstream for this request
`COALESCED`	Merged with an identical concurrent request that shared one upstream fetch
`STALE`	The upstream had a brief problem, so data up to 30 seconds old was returned
`BUSY`	The upstream call budget is temporarily used up; retry shortly (returns 503)
`BYPASS`	This request is not cached

For high-frequency trading that needs millisecond latency, connect to the data source or exchange directly instead of relying on cached market data.