Shipwell · Rate Limits

Shipwell Rate Limits

Shipwell does not publish fixed numeric rate limits in its public developer documentation. Access is company-scoped by API key, and usage is governed by the platform contract rather than a documented per-minute request cap. Clients should treat the API as rate-limited in principle - handle HTTP 429 responses with exponential backoff and honor any Retry-After header - and confirm exact limits with Shipwell for a given account. A fully separate sandbox environment exists for development and testing, where external integrations return mocked responses.

Shipwell Rate Limits is the machine-readable rate-limit profile for Shipwell on the APIs.io network, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Transportation Management, TMS, Freight, Logistics, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Transportation ManagementTMSFreightLogisticsRate LimitingQuotas

Limits

Core API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the v2 Core API. API keys are company-scoped.
Events and Webhooks account
deliveries
not published
Webhook deliveries are server-to-endpoint HTTP POST calls; no documented delivery-rate cap.
Sandbox Usage account
requests
not published
Sandbox is separate from production and mocks third-party integrations; limits not documented.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 response.
Idempotency and Environments
Production and sandbox are fully separate; objects created in one environment cannot be manipulated from the other.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/shipwell-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.