Commerce Layer · Rate Limits

Commercelayer Rate Limits

The Commerce Layer Core API enforces per-organization rate limits on API requests over a sliding time window, returning HTTP 429 when the limit is exceeded. Limits differ between read and write operations and between the test and live environments, and the response carries headers describing the current limit, remaining requests, and reset time. Specific per-window request counts are not reconciled in this artifact and should be confirmed against the provider documentation and live response headers.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include Commerce, Headless, Composable, eCommerce, and JSON:API.

3 Limits Throttle: 429
CommerceHeadlessComposableeCommerceJSON:APIRate LimitingQuotasThrottling

Limits

API Requests organization
requests
see provider documentation
Per-organization request limit over a sliding window; HTTP 429 on exceed.
Read Requests organization
requests
see provider documentation
GET / read operations may have a higher allowance than writes.
Write Requests organization
requests
see provider documentation
POST / PATCH / DELETE operations may have a lower allowance than reads.

Policies

Environment Differences
Test and live organizations may have different limits.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor rate-limit reset headers before retrying.

Sources