Track a FedEx shipment and receive real-time status updates via the FedEx Track API and Shipment Visibility Webhooks
domain: developer.fedex.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the FedEx OAuth token endpoint to obtain a bearer token
POST to https://apis.fedex.com/track/v1/trackingnumbers with a JSON body containing the trackingInfo array (each entry has trackingNumberInfo.trackingNumber)
Parse the output.completeTrackResults[].trackResults[].scanEvents array for the latest status, timestamps, and locations
In the FedEx Developer Portal, create a Shipment Visibility Webhook project and register an HTTPS endpoint URL to receive push notifications
Handle incoming webhook POST payloads by verifying the signature header and extracting event type and shipment status
Respond to FedEx webhook deliveries with HTTP 200 within the required timeout to prevent retries
Known gotchas
The Shipment Visibility Webhook is currently available for U.S.-based FedEx accounts only; international tracking must rely on polling the Track API
Tracking numbers for multi-piece shipments (MPS) return results for all pieces; index by packageSequenceNumber to display per-package status rather than overwriting a single status field
FedEx tokens expire; if a webhook payload arrives and the stored token is stale, re-authenticate before making any follow-up API calls triggered by the event
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?