Ordergroove · Rate Limits

Ordergroove Rate Limits

Ordergroove enforces a documented per-IP rate limit on its REST API. All endpoints under restapi.ordergroove.com (and staging.restapi.ordergroove.com) are limited to 6,000 requests per IP address per one-minute window. Requests over the threshold receive an HTTP 429 Too Many Requests response, which Ordergroove documents as safe to retry at any time. The docs recommend optimizing code, regulating request rates, and implementing retry logic for 429s. Cursor-based pagination is used to traverse large data sets efficiently.

Ordergroove Rate Limits is the machine-readable rate-limit profile for Ordergroove 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 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Subscriptions, eCommerce, Rate Limiting, and Quotas.

3 Limits Throttle: 429
SubscriptionseCommerceRate LimitingQuotas

Limits

REST API Requests ip
requests
6000
6,000 requests per IP address per minute across all REST endpoints; 429 when exceeded.
Staging REST API Requests ip
requests
6000
Same 6,000/IP/minute limit applies on staging.restapi.ordergroove.com.
Bulk Operations account
requests
permission-gated
Listing subscriptions/orders across more than one customer requires the Bulk Operations permission on the Application API scope.

Policies

Retry Safe
429 Too Many Requests responses are documented as safe to retry at any point in time.
Backoff Strategy
Regulate request rate and implement retry logic with exponential backoff and jitter for 429 responses.
Cursor Pagination
Large result sets are traversed with cursor-based pagination rather than large single responses.

Sources