Track a shipment
GET https://www.wearewarp.com/api/v1/track?booking_id=...
Returns three things in one call: the original booking row, live carrier status, and the event timeline. Pass the shipment_id or shipment_number from the book response as booking_id. Bearer auth with your wak_ key; the same self serve key from /agents/account covers quote, book, and track.
Request
- booking_id -- query parameter, required. The shipment id from your booking confirmation.
curl example
curl "https://www.wearewarp.com/api/v1/track?booking_id=S-80215-2616" \
-H "Authorization: Bearer wak_live_YOUR_KEY"MCP tool call
{
"tool": "track",
"args": { "booking_id": "S-80215-2616" }
}CLI example
warp-agent track S-80215-2616Response
{
"shipment_id": "...",
"lane_id": "ln_900_100",
"mode": "ltl",
"origin_zip": "90001",
"destination_zip": "10001",
"pickup_date": "...",
"delivery_date": "...",
"price_usd": 485.00,
"status": "in_transit",
"schedule_live": true,
"pickup_window": { "kind": "appointment", "from": "...", "to": "..." },
"delivery_window": { "kind": "scheduled", "from": "...", "to": "..." },
"tracking_dashboard": "https://customer.wearewarp.com/shipment/S-80215-2616",
"upstream_tracking": { "status": "..." },
"events": [ "..." ]
}Works beyond the agent API
Any Warp booking is trackable.
If the booking was made outside the agent API, for example in the customer portal, the endpoint still attempts live upstream tracking so your agent gets status instead of a dead end. Sandbox shipment ids return production shaped responses with an explicit sandbox flag.
If the booking was made outside the agent API, for example in the customer portal, the endpoint still attempts live upstream tracking so your agent gets status instead of a dead end. Sandbox shipment ids return production shaped responses with an explicit sandbox flag.
Errors
- MISSING_BOOKING_ID -- the booking_id query parameter is required.
- 404 with upstream_status -- the id is not a Warp booking your key can see.