FedEx Tracking API for Developers

Use C2W Package Tracking API to retrieve FedEx shipment information through RapidAPI. The documented endpoint accepts a tracking number and returns JSON for your application. Webhooks are not supported.

How to request FedEx tracking

Subscribe on RapidAPI and keep your credentials on your server.
Send your shipment’s tracking number as trackingNumber to GET /TrackingPackage.
Check the HTTP response before reading tracking fields. Use the API reference for headers and schema.

curl --get 'https://trackingpackage.p.rapidapi.com/TrackingPackage' \
  --data-urlencode 'trackingNumber=YOUR_TRACKING_NUMBER' \
  --header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \
  --header 'X-RapidAPI-Host: trackingpackage.p.rapidapi.com'

Add an Authorization header only if it was issued for your integration. This example uses a placeholder; it does not query a real shipment.

Illustrative response, not a live shipment

This synthetic subset illustrates documented field names. It is not a recorded FedEx response or a guarantee that every shipment supplies these values.

{
  "TrackingNumber": "YOUR_TRACKING_NUMBER",
  "Carrier": "FedEx",
  "Delivered": false,
  "Status": "In transit"
}

See authentication and error handling. Keep credentials server-side and treat network failures separately from shipment status.

Plan polling and cost before subscribing

Webhooks are not supported. Your application schedules requests and customer notifications. Results may be cached; a successful call does not imply a new carrier scan.

Example: 25 active shipments checked four times per day use 100 requests, before retries and manual refreshes. The Pro plan includes 150 requests/day at $9.99/month, leaving 50 requests of headroom. This is a workload example, not a recommended polling interval.

The free plan includes 5 requests/day for evaluation. Space requests within the rate limit and stop routine polling when your workflow is complete. Compare plans and request budgets; confirm applicable terms in RapidAPI.

Keep service, status, and delivery time separate.

A tracking dashboard needs more than one status label. Keep the service name separate from shipment progress, and preserve delivery timestamps exactly until their timezone semantics are established.

Map your existing response fields

The C2W reference includes ServiceType, Delivered, and DeliveredDateTime. Map these intentionally when migrating; field names in a direct FedEx response differ from the C2W schema. Older illustrative examples may use different delivery-date names.

Do not infer proof-of-delivery access

A delivered flag or signature name is not the same as a downloadable signature image. Confirm any proof-of-delivery requirement separately. FedEx documents its own signature proof-of-delivery access requirements in the FedEx tracking reference; those do not establish C2W feature availability.

Follow the FedEx integration walkthrough for the broader workflow.

Fields to consider in your application

Integration considerations, not guaranteed field availability
Field	Application handling
`ServiceType`	Keep the carrier service distinct from the current status.
`DeliveredDateTime`	Display available delivery time without inventing a UTC offset.
`SignatureName`	Treat unavailable values as missing; do not imply signature-image access.

Available values depend on the shipment and carrier data. Empty strings, null values, and absent fields should not break your interface. These are schema notes, not a recorded FedEx production response.

Before going live

Test delivered, in-transit, unavailable-data, and exception cases for your services. Establish your polling schedule, request headroom, and support process. Use our integration guide and request-budget examples.