Order Desk · Rate Limits

Orderdesk Rate Limits

The Order Desk API is rate limited with a leaky-bucket algorithm. Each store starts with a bucket of 20 requests that refills at 3 requests per second, which works out to roughly 100 requests available over a rolling 30-second window. The number of requests remaining is returned on every response in the X-Tokens-Remaining header. When the bucket is empty the API returns HTTP 429 and includes an X-Retry-After header indicating how many seconds to wait before retrying.

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

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

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

Tagged areas include Ecommerce, Order Management, Rate Limiting, and Quotas.

3 Limits Throttle: 429
EcommerceOrder ManagementRate LimitingQuotas

Limits

Leaky Bucket Capacity store
requests
20 requests (initial bucket)
Each store's bucket holds up to 20 requests before throttling.
Refill Rate store
requests
3 requests per second
The bucket refills at 3 requests/second, ~100 requests per rolling 30-second window.
List Page Size request
records
500 (max limit parameter, default 50)
The limit query parameter caps records returned per list request.

Policies

Remaining Quota Header
Every response includes X-Tokens-Remaining showing how many requests are left in the bucket.
Retry-After
429 responses include X-Retry-After with the number of seconds to wait before retrying.
Backoff Strategy
Clients should throttle to about 3 requests/second, watch X-Tokens-Remaining, and honor X-Retry-After with exponential backoff on 429 responses.

Sources