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 rate-limit profile for AfterShip on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-08-27.

It captures 20 rate-limit definitions, including Tracking API POST /trackings — POST /trackings 20; Tracking API GET /trackings — GET /trackings 6; Tracking API GET /trackings/:id — GET /trackings/:id 5.

Limit state is signalled in the X-RateLimit-Reset, X-RateLimit-Limit, X-RateLimit-Remaining, and rateLimit-reset response headers, and an exhausted limit returns HTTP 429.

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 Exhausted: HTTP 429 X-RateLimit-ResetX-RateLimit-LimitX-RateLimit-RemainingrateLimit-reset
Transcribed from the provider's documentation on 2026-08-27 — www.aftership.com/docs/tracking/quickstart/rate-limit.
View Source
ShippingTrackingE-CommercePost-PurchaseNotificationsRate LimitingQuotasThrottling

Limits

Tracking API POST /trackings per-endpoint per-organization
POST /trackings 20
POST /trackings
· per 1 second
20
Tracking API GET /trackings per-endpoint per-organization
GET /trackings 6
GET /trackings
· per 1 second
6
Tracking API GET /trackings/:id per-endpoint per-organization
GET /trackings/:id 5
GET /trackings/:id
· per 1 second
5
Tracking API PUT /trackings/:id per-endpoint per-organization
PUT /trackings/:id 5
PUT /trackings/:id
· per 1 second
5
Tracking API DELETE /trackings/:id per-endpoint per-organization
DELETE /trackings/:id 5
DELETE /trackings/:id
· per 1 second
5
Tracking API POST /trackings/:id/retrack per-endpoint per-organization
POST /trackings/:id/retrack 5
POST /trackings/:id/retrack
· per 1 second
5
Tracking API POST /trackings/:id/mark-as-completed per-endpoint per-organization
POST /trackings/:id/mark-as-completed 5
POST /trackings/:id/mark-as-completed
· per 1 second
5
Tracking API POST /couriers/detect per-endpoint per-organization
POST /couriers/detect 3
POST /couriers/detect
· per 1 second
3
Tracking API GET /couriers per-endpoint per-organization
GET /couriers 5
GET /couriers
· per 1 second
5
Tracking API POST /estimated-delivery-date/predict per-endpoint per-organization
POST /estimated-delivery-date/predict 5
POST /estimated-delivery-date/predict
· per 1 second
5
Tracking API POST /estimated-delivery-date/predict-batch per-endpoint per-organization
POST /estimated-delivery-date/predict-batch 20
POST /estimated-delivery-date/predict-batch
· per 1 second
20
Tracking API POST /courier-connections per-endpoint per-organization
POST /courier-connections 5
POST /courier-connections
· per 1 second
5
Tracking API GET /courier-connections per-endpoint per-organization
GET /courier-connections 5
GET /courier-connections
· per 1 second
5
Tracking API GET /courier-connections/:id per-endpoint per-organization
GET /courier-connections/:id 5
GET /courier-connections/:id
· per 1 second
5
Tracking API PATCH /courier-connections/:id per-endpoint per-organization
PATCH /courier-connections/:id 5
PATCH /courier-connections/:id
· per 1 second
5
Tracking API DELETE /courier-connections/:id per-endpoint per-organization
DELETE /courier-connections/:id 5
DELETE /courier-connections/:id
· per 1 second
5
Shipping API default per-organization
· per 1 second
10/1 second
Returns API default per-organization
· per 1 second
10/1 second
Tracking plan ceiling (Premium) per-plan
· per 1 second
10/1 second
The Tracking pricing page states "Premium: 10 req/sec rate limit" for the API & webhooks entitlement.
Public MCP fair-use limit per-client (shared public endpoint)
· per unstated
mcp.aftership.com applies an undisclosed fair-use limit. Probed 2026-08-27: POST https://mcp.aftership.com/tracking/public returned HTTP 429 with ratelimit-limit: 100000, ratelimit-remaining: 0, retry-after: 31090 and meta.type TooManyRequests / meta.source gateway. Automated or bulk use is explicitly not permitted.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429.

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/aftership-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.