Authenticate via UPS OAuth 2.0 to obtain a Bearer token
POST to /api/track/v1/subscription/anchor with your callback URL, tracking number, locale, and transaction type to register a webhook subscription for a specific shipment
UPS will POST status events to your callback URL as shipment milestones occur; each payload includes tracking number, activity description, location, and timestamp
Return HTTP 200 from your callback within the required timeout; failed callbacks trigger UPS retries
To unsubscribe from alerts for a shipment, DELETE /api/track/v1/subscription/{subscriptionId}
Known gotchas
The UPS Track Alert API (push) is distinct from the polling-based UPS Tracking API; subscriptions must be created per shipment, not per account
UPS OAuth 2.0 is required for all API calls since the retirement of legacy access-key auth in June 2024
Callback endpoints must be HTTPS and return 200 quickly; UPS may de-register subscriptions that consistently fail to acknowledge delivery within the timeout window
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp