Nacelle · Rate Limits

Nacelle Rate Limits

Nacelle does not publish explicit numeric request-per-minute quotas for its Storefront GraphQL API. Instead, the documentation defines hard per-request constraints: a 10 MB maximum response payload and a 20-second request timeout. Automatic Persisted Queries (APQ) are supported so repeated queries can be cached at the CDN edge with roughly a 60-second TTL, reducing origin load. Any account-level throttling is governed by enterprise contract terms rather than a public rate card.

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

It captures 3 rate-limit definitions, measuring bytes, seconds, and requests.

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

Tagged areas include Commerce, Headless Commerce, GraphQL, Rate Limiting, and Quotas.

3 Limits Throttle: 429
CommerceHeadless CommerceGraphQLRate LimitingQuotasThrottling

Limits

Response Payload Size request
bytes
10 MB
Maximum size of a single Storefront GraphQL response payload.
Request Timeout request
seconds
20
Storefront GraphQL requests time out after ~20 seconds.
Per-Account Throttling account
requests
see enterprise contract
No public per-minute quota; governed by contract terms.

Policies

Automatic Persisted Queries (APQ)
Persisted queries let repeated Storefront requests be served from the CDN edge cache (~60s TTL), lowering origin request pressure.
Pagination
Use Relay-style cursor pagination (first / after) to bound response size and stay within the 10 MB payload and 20s timeout limits.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.

Sources