Subscribe to UPS Track Alert API for push webhook notifications on shipment status changes
domain: ups.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your webhook callback URL via POST /api/track/v1/subscription with a JSON body containing 'locale', 'countryCode', 'trackingNumberList' (array of tracking numbers), and 'destination' object with 'url' and a 'credentialList' for HMAC signature verification.
UPS signs webhook payloads with an HMAC-SHA256 signature sent in the 'X-Hub-Signature' header; validate this against the raw request body using your credential secret before processing the payload.
The webhook payload 'trackResponse.shipment' structure mirrors the polling GET response; extract event data from 'package[0].activity' in the payload.
To unsubscribe, DELETE /api/track/v1/subscription/{subscriptionId} using the subscription ID returned at registration time.
Respond with HTTP 200 within a few seconds; UPS will retry delivery if it does not receive a timely 2xx response, so process asynchronously.
Known gotchas
Each subscription is tied to a specific list of tracking numbers; you must register new tracking numbers as new subscriptions rather than modifying an existing subscription in place.
UPS Track Alert webhooks require your endpoint to be publicly reachable over HTTPS with a valid TLS certificate; self-signed certificates are rejected.
Subscription registration is separate from the standard UPS OAuth flow — ensure you are using the correct API product entitlements for Track Alert in your UPS developer application.
Give your agent this knowledge — and 6,400+ more routes
One MCP install gives any agent live access to the full route map across 2,100+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp