AfterShip actually runs two separate APIs under one dashboard: the Tracking API, which pulls shipment status and events from hundreds of carriers, and the Shipping API, the product AfterShip still calls Postmen in parts of its own docs, which quotes multi-carrier rates and buys labels. Having access to either one doesn't mean a business has it built into anything yet. We take the tracking events and label data AfterShip's API already returns and wire them into the order system, support desk, or warehouse process that's currently waiting on a person to relay them.
The Tracking API pulls shipment status on demand or by webhook. A request against a tracking number returns the carrier history AfterShip has aggregated, and a webhook can push a status change the moment it happens instead of making your system poll for it.
The Shipping API, still called Postmen in places, handles rates and labels. It quotes a shipment against whichever carriers you've connected, returns an option by whatever rule you set, cheapest, fastest, preferred carrier, and generates the label, the same job ShipEngine or EasyPost do for other businesses.
Authentication is a single API key from the AfterShip dashboard. There's no OAuth flow to set up before the first real request goes out, which is part of why the gap usually isn't getting access. It's deciding what the rest of the business should actually do with what comes back.
An API key proves you can call AfterShip. It doesn't decide which carrier wins a rate comparison, what happens when a tracking webhook reports a delay, or where a generated label needs to land next. Those are business rules, and somebody has to write them down and build them, usually after the first integration anyone did only covered whichever single workflow it was built for on day one.
A quote comes back from AfterShip's Shipping API, a rule picks the carrier by cost or delivery speed, and the label gets created, instead of a person comparing options in the dashboard for every single order.
A status change from the Tracking API lands as a webhook, and instead of sitting in a log nobody watches, it opens a support flag or sends a proactive message to the customer on its own.
Tell us what you're pulling from AfterShip's Tracking or Shipping API today, and we'll look at how much of what happens after that response still gets done by hand.
Tell us what you're calling, the Tracking API, the Shipping API, or both, and what still happens manually once the response comes back. We'll work out what's worth building directly into your stack. AfterShip's API is just one example here; the same gap between having access and having it wired in shows up with nearly every tool a business already pays for.
Let's talk →Two separate APIs under one AfterShip account: a Tracking API for pulling shipment status and events from hundreds of carriers, and a Shipping API, internally still referred to as Postmen, for multi-carrier rate quoting and label generation.
Postmen was AfterShip's original standalone shipping API product. AfterShip folded it into its own suite and now calls it the AfterShip Shipping API, though the Postmen name still appears in parts of the documentation and in older developer discussion.
From inside your AfterShip account, under the developer or API settings. No OAuth setup is required to start, just the key tied to your account.
The Tracking API aggregates data from several hundred carriers worldwide, and the Shipping API supports a smaller but still broad set for rate quoting and label purchase. Exact coverage depends on which carriers you've connected in your own account.