Monitor usage
Response fields
The dashboard also shows daily usage and plan details.
Throttled responses
When you exceed per-minute or daily quotas, the API returns HTTP429:
Retry-After header (seconds). Honor it before retrying.
Plan limits on historical queries
Historical endpoints also enforce resolution and lookback. Violations return HTTP403:
Recommended client behavior
Respect Retry-After
Respect Retry-After
On
429, read the Retry-After header and sleep at least that many seconds before retrying.Exponential backoff
Exponential backoff
If
Retry-After is absent, use increasing delays (e.g. 1s → 2s → 4s) with a maximum retry cap.Connection reuse
Connection reuse
Reuse HTTP connections with
requests.Session (Python) or httpx.Client to reduce TLS overhead.Bulk access patterns
Bulk access patterns
Paginate with cursors instead of unbounded parallel fan-out. Pace sequential history calls (~200ms) when backfilling many markets.
Resolution selection
Resolution selection
Use the coarsest
resolution that meets your analysis needs — fewer buckets, fewer pages, lower quota usage.