The shipment tracking API.
One POST creates a tracker. Signed webhooks deliver every status change, normalized across 100+ carriers. Test mode is free and needs no card.
Test mode is free. No card required.
Sample data — live responses have exactly this shape.
From carrier chaos to one clean event
Follow one shipment through Shipyu — from the raw carrier scan to the moment your customer sees it.
One status model across carriers
Every carrier phrases the same scan differently. Shipyu normalizes them into one documented event model, so your code handles in_transit once — not once per carrier.
Delivery events that arrive
Webhooks are HMAC-signed and retried on a backoff schedule until your endpoint confirms. Every attempt is visible, replayable, and pausable from the console.
Trace every update end to end
Follow one shipment from raw carrier payload to the webhook your app received. Request logs, tracker timelines, and deliveries cross-link everywhere.
One canonical shipment model across every supported carrier.
Carrier APIs describe the same delivery process in different ways. Shipyu converts those differences into predictable statuses, events, locations, and delivery estimates your application can use — the same fields, the same meanings, on every carrier.
Delete your carrier integrations
- One documented event model instead of per-carrier parsers
- Debug real requests and webhook attempts in the console
- Deterministic TEST_ scenarios — build before you pay
- Keys with rotation, roles, and org-scoped access
Ship tracking experiences faster
- Consistent status language across every carrier
- Add carriers without rebuilding the product
- Estimated delivery dates on the tracker object
- Branded tracking pages backed by the same API
See stalled shipments before customers do
- Tracker inspector answers “why has this not moved”
- Carrier exceptions surfaced on one timeline
- Webhook delivery health at a glance
- Escalate with evidence: request ids and raw payloads
Built for critical delivery infrastructure
Operate customer-facing tracking reliably across every carrier — with the controls your security review expects.
Security
- Org-scoped roles for keys, webhooks, and billing
- Hashed keys with timing-safe verification
- PII scrubbing in stored request bodies
- 90-day retention with automatic cleanup
Reliability
- Signed webhooks with five-step retry backoff
- Idempotent event processing
- Rate limits that fail loud, not silent
- Full request audit trail with request ids
Support
- Implementation and migration guidance
- Priority support for volume plans
- Contract pricing above one million trackers
- Talk to the people who built it
Tracking is the beginning.
Shipyu is building a normalized logistics data layer for modern applications. We are starting with shipment tracking, where fragmented carrier systems create immediate engineering and operational costs.
Questions
What is Shipyu?
Shipyu is a shipment tracking API for developers. You send one POST with a tracking number; Shipyu identifies the carrier, polls for scans, normalizes every carrier's status vocabulary into a single model, and delivers each change to your endpoint as an HMAC-signed webhook. It covers 100+ carriers including USPS, UPS, FedEx, and DHL.
Which carriers does Shipyu support?
100+ carriers, including USPS, UPS, FedEx, DHL, and a long tail of regional and international carriers. You can pass a carrier explicitly or omit it and let Shipyu detect it from the tracking number format.
What does it mean that statuses are normalized?
Carriers describe the same physical event differently — one says "Departed sort facility", another "Processed through network", another "Linehaul departure". Shipyu maps all of them onto one status model, so your code branches on a stable vocabulary instead of per-carrier strings. The original carrier payload is preserved alongside it, so nothing is lost.
How does Shipyu deliver tracking updates — polling or webhooks?
Webhooks. Shipyu polls the carriers so you do not have to, and pushes every status change to your endpoint. Deliveries are HMAC-SHA256 signed as t=<timestamp>,v1=<signature> so you can verify origin and reject replays, and failed deliveries retry five times at 1 minute, 5 minutes, 30 minutes, 2 hours, and 12 hours with jitter. You can still read any tracker on demand, but you should not need to poll.
Can AI agents use Shipyu?
Yes. Shipyu runs an official MCP server, so Claude Code, Cursor, and other MCP clients can create trackers, read shipment status, manage webhooks, and check usage directly. Test keys are free, so an agent can verify an entire integration without spending anything.
Is Shipyu a shipping label API?
No. Shipyu is focused on tracking — knowing where a parcel is and being told when that changes. If you need a full post-purchase suite with branded tracking pages and returns management, or the broadest possible carrier network, other products cover that ground and we compare against them honestly.
Billing questions are answered on pricing, and we compare Shipyu against other tracking APIs on comparisons.
Build reliable shipment tracking without maintaining carrier integrations
Create a key and make your first call in minutes. Pay only when you go live.