All of these reads retain app authorization and visibility checks. Supply
x-app-id; backend API keys belong on the server, not in browser Worker assets. Inspect delivery state, freshness, null snapshot entries, and per-item errors rather than treating an empty HTTP 200 response as a healthy chart or book.
The scoped quotas apply in addition to existing global quotas, combine instant/full search into one family, and charge outcome snapshot batches by distinct outcome IDs; the active single-outcome route shares that budget at one unit per read. A 429 includes Retry-After in seconds; unavailable scoped limiting returns 503 with a retry hint. Neither response belongs in a shared cache. See the complete quota and retry rules.
For detailed API schemas, use the API Reference tab. For integration patterns, see real-time charts, WebSocket orderbooks, and server API keys.