Shipping API vs Tracking API: which one do you need?
They sound alike and are often sold by the same company, but they solve different problems and are priced in different units.
Two jobs, two products
A shipping API creates shipments. You send an origin, a destination and a parcel; it returns rates, and when you choose one it returns a label and a tracking number. Its natural billing unit is the label.
A tracking API follows shipments that already exist. You register a tracking number — from any source — and receive status events, usually normalised across carriers and often pushed by webhook. Its natural billing unit is the tracked shipment.
When a shipping API's tracking is enough
Most shipping APIs track the labels they issue. If every parcel you send is created through one platform, you may not need anything else. Check two things in the documentation: whether tracking events are pushed by webhook, and whether tracking is included in the label fee.
When you need a dedicated tracking API
- Labels come from several systems: a 3PL, a marketplace, a carrier portal.
- You want one status model across every carrier for notifications and support.
- You need to track numbers you did not create.
See Tracking APIs and Shipping APIs for products in each family.
Do not compare the prices directly
A per-label fee and a per-tracking fee measure different things. On this site each product shows its pricing unit, and the compare tool warns when you mix product types.
We link to official docs, pricing and terms. Unconfirmed fields stay marked as unknown.