ShipBob · Rate Limits
Shipbob Rate Limits
ShipBob enforces a sliding-window rate limit of 150 requests per minute, totalled per user, per application across all ShipBob Developer API endpoints. Exceeding the limit returns HTTP 429 with `x-retry-after` (seconds to wait) and `x-remaining-calls` headers.
Shipbob Rate Limits is the machine-readable rate-limit profile for ShipBob on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Logistics, Fulfillment, E-Commerce, 3PL, and Warehousing.
1 Limits
Throttle: 429
LogisticsFulfillmentE-Commerce3PLWarehousingRate LimitingQuotasThrottling
Limits
Global Sliding Window user + application
150
Counted across all ShipBob Developer API endpoints (channels, orders, products, inventory, receiving, returns, webhooks, locations, billing, simulations).
Policies
Backoff Strategy
Clients should honor the `x-retry-after` header on 429 responses and implement exponential backoff with jitter for unhandled throttling cases.
Pre-Emptive Throttling
Inspect `x-remaining-calls` in responses and slow down before the window is exhausted.
Per-Application Isolation
Spread workload across multiple OAuth applications when integrating multiple high-volume use cases to avoid contention against a single 150/min budget.
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.