AfterShip · Rate Limits
Aftership Rate Limits
Published AfterShip rate limits. From API version 2024-07 the Tracking API moved from a flat 10 req/sec per organization to a PER-ENDPOINT limit; Shipping and Returns remain a flat 10 req/sec per organization.
Aftership Rate Limits is the machine-readable rate-limit profile for AfterShip on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 20 rate-limit definitions.
The profile also includes 1 backoff/retry policy defined and response codes documented for throttled and meta_type.
Tagged areas include Shipping, Tracking, E-Commerce, Post-Purchase, and Notifications.
20 Limits
Throttle: 429
ShippingTrackingE-CommercePost-PurchaseNotificationsRate LimitingQuotasThrottling
Limits
Tracking API POST /trackings per-endpoint per-organization
20
Tracking API GET /trackings per-endpoint per-organization
6
Tracking API GET /trackings/:id per-endpoint per-organization
5
Tracking API PUT /trackings/:id per-endpoint per-organization
5
Tracking API DELETE /trackings/:id per-endpoint per-organization
5
Tracking API POST /trackings/:id/retrack per-endpoint per-organization
5
Tracking API POST /trackings/:id/mark-as-completed per-endpoint per-organization
5
Tracking API POST /couriers/detect per-endpoint per-organization
3
Tracking API GET /couriers per-endpoint per-organization
5
Tracking API POST /estimated-delivery-date/predict per-endpoint per-organization
5
Tracking API POST /estimated-delivery-date/predict-batch per-endpoint per-organization
20
Tracking API POST /courier-connections per-endpoint per-organization
5
Tracking API GET /courier-connections per-endpoint per-organization
5
Tracking API GET /courier-connections/:id per-endpoint per-organization
5
Tracking API PATCH /courier-connections/:id per-endpoint per-organization
5
Tracking API DELETE /courier-connections/:id per-endpoint per-organization
5
Shipping API default per-organization
10
Returns API default per-organization
10
Tracking plan ceiling (Premium) per-plan
10
Public MCP fair-use limit per-client (shared public endpoint)
Policies
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429.
Sources
- https://www.aftership.com/docs/tracking/quickstart/rate-limit
- https://www.aftership.com/docs/shipping/quickstart/rate-limit
- https://www.aftership.com/docs/returns/quickstart/rate-limit
- https://www.aftership.com/pricing
- https://github.com/AfterShip/tracking-and-returns-mcp
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.