AfterShip Tracking
Book shipments and track deliveries with AfterShip Tracking straight from your orders, with no re-typing.
14 ways to read, 4 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with AfterShip Tracking, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Mark tracking completedApproval by rule
- Retrack trackingApproval by rule
- List courier connectionsRead
Example flow
- AfterShip Tracking · List courier connectionsDone
- AfterShip Tracking · Mark tracking completedNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches AfterShip Tracking.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to AfterShip Tracking
- AfterShip Tracking's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write AfterShip trackings across 1,200+ couriers, detect couriers, predict delivery dates, and read AfterShip Shipping carrier accounts and rate quotes.
AfterShip API docs- Source actions
- 14
- Destination actions
- 4
- Data types
- 12
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Courier connections2
- Get courier connectionSource
Read one courier connection's carrier and dates, without credentials.
- List courier connectionsSource
List the carrier accounts connected to AfterShip, without their stored credentials.
Courier detections1
- Detect courierSource
Couriers that match a tracking number.
Couriers1
- List couriersSource
Couriers supported by AfterShip, or only those activated on the account.
Estimated delivery dates batch1
- Predict delivery dates (batch)Source
Predict delivery dates for up to five courier, service and route combinations at once.
Estimated delivery dates1
- Predict delivery dateSource
Predict the delivery date for a courier, service and route before or after shipping.
Shipper accounts2
- Get shipping shipper accountSource
One AfterShip Shipping carrier account. Credentials are never returned.
- List shipping shipper accountsSource
Carrier accounts connected to AfterShip Shipping, used to quote rates. Credentials are never returned.
Shipping rate quotes1
- Quote shipping ratesSource
Quote rates from your connected carrier accounts for a shipment, one record per service. Quoting buys nothing.
Shipping rates2
- Get shipping rate requestSource
One AfterShip Shipping rate calculation with its quoted rates.
- List shipping rate requestsSourceIncremental
Rate calculations made through AfterShip Shipping, with every quoted rate.
Tracking checkpoints1
- List tracking checkpointsSource
Every checkpoint of one tracking, one record per checkpoint, oldest first.
Tracking completions1
- Mark tracking completedDestinationProvider duplicate protectionApproval before production
Mark a tracking as delivered, lost or returned to sender and stop tracking.
Tracking retracks1
- Retrack trackingDestinationNot retried automaticallyApproval before production
Reactivate an expired tracking (at most three times).
Trackings4
- Create trackingDestinationProvider duplicate protectionApproval before production
Start tracking a shipment, with order and customer context.
- Get trackingSource
One tracking with checkpoints, optionally translated.
- List trackingsSourceIncremental
Trackings with status, ETAs and checkpoints, filtered by update time or tag.
- Update trackingDestinationProvider duplicate protectionApproval before production
Update a tracking's order, customer, courier and destination details.
Access and limits
- Authentication
- AfterShip API key
- Plans and access
- AfterShip Tracking plans include API access; tracking volume counts against the plan's shipment quota. Estimated delivery date prediction requires the EDD add-on. Each created tracking consumes plan quota; trackings older than 120 days are not returned by list.
- Test environment
- Use a trial account and AfterShip's testing-courier slug for test trackings.
- Rate limits
- Per endpoint per second: POST /trackings 20, GET /trackings 6, single tracking reads and updates 5, courier detect 3, couriers 5; HTTP 429 with X-RateLimit-Reset.
- Pagination
- cursor and limit (max 200) with data.pagination.next_cursor and has_next_page.
- Provider events
- Webhooks for tracking updates (tag and checkpoint changes), signed with HMAC. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- No customer notifications are sent and nothing is deleted. Deleting trackings and creating, updating or deleting courier connections (which carry carrier credentials) are intentionally excluded; courier connections are read-only and never return credentials.
- Tracking API 2026-07 has no Returns, Notifications or Tracking Pages endpoints. Notification subscriber reads exist only in the deprecated 2023-10 version and are not added. Returns API reads are not added because AfterShip's Returns reference (aftership.com/docs/returns) could not be retrieved for verification (HTTP 403) and no official Returns SDK is published.
- Shipping (AfterShip Shipping API, formerly Postmen, /postmen/v3) is read-only here: shipper accounts (never credentials) and rate quotes and their history. Paths, query parameters and fields follow AfterShip's official shipping-sdk-java. Label creation (billable), label and pickup cancellation, pickups, manifests, address validation (beta) and shipper account create, update, credential and delete calls are excluded. The API key needs Shipping access, and Shipping production keys only work against api.aftership.com (sandbox keys use sandbox-api.aftership.com, which this connector does not call).
- Trackings are addressed by AfterShip ID in this API version; use trackings.list with trackingNumbers to find an ID.
- Creating a tracking that already exists for the same slug and tracking number returns HTTP 400 (meta code 4003) and does not create a duplicate.
- trackings.list returns trackings from the last 120 days only.
- Retracking is allowed only for expired trackings and at most three times.
Developer reference
- Create the AfterShip credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose AfterShip Tracking, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/aftership and the Connections API.