Circana · Rate Limits

Circana Rate Limits

Circana does not publish a public rate-limit policy for its Liquid Data, Unify+, or Intelligence Suite APIs. Practical limits are governed by the client's contracted data scope and query envelope and are enforced by the Circana platform team (deployed on Azure / AWS / GCP / Oracle Cloud / Snowflake). Bulk integration is preferred via cloud data shares (Snowflake, BigQuery) and pre-built connectors rather than high-frequency point queries.

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

It captures 2 rate-limit definitions, measuring varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, unauthorized, forbidden, serverError, and serviceUnavailable.

Tagged areas include Analytics, Business Intelligence, Consumer Data, CPG, and Market Research.

2 Limits Throttle: 429
AnalyticsBusiness IntelligenceConsumer DataCPGMarket ResearchRetailRate Limiting

Limits

Liquid Data API requests tenant
varies
see Circana customer integration documentation; not publicly documented
Limits are tied to contracted data scope and integration channel (point API vs cloud share).
Cloud share queries tenant
varies
governed by underlying warehouse (Snowflake / BigQuery / Databricks)
Query throughput is bounded by the client's own warehouse compute, not by a Circana cap.

Policies

Backoff Strategy
On 429 / 5xx, retry with exponential backoff and jitter; honor Retry-After when present.
Bulk Over Polling
Prefer Snowflake / BigQuery / Databricks data-share consumption and the Intelligence Suite connectors over high-frequency point API calls.
Scoped Access
API access is scoped to the categories, geographies, and panels in the customer contract; out-of-scope queries return 403 / authorization errors rather than throttling.

Sources