Track shipments in your application.

Carriers have wildly different tracking event codes. The RC:Ship Tracking API ingests raw carrier events and maps them to a normalized status schema, so you only have to integrate tracking logic once.

Tracking Lookup

You can look up the tracking history of any shipment by passing its carrier tracking number (AWB) or the RC:Ship shp_... ID.

curl https://api.ship.retailcoder.com/v1/tracking/AMZ987654321 \
  -H "Authorization: Bearer sk_live_your_api_key_here"

Tracking Response

The response contains the current overall status, as well as an array of events providing a chronological timeline of the shipment.

{
  "trackingNumber": "AMZ987654321",
  "carrier": "amazon_shipping",
  "status": "in_transit",
  "estimatedDeliveryDate": "2024-05-20T18:00:00Z",
  "events": [
    {
      "status": "in_transit",
      "description": "Package has left the carrier facility.",
      "location": "Mumbai, MH",
      "timestamp": "2024-05-19T08:14:00Z"
    },
    {
      "status": "picked_up",
      "description": "Package picked up by carrier.",
      "location": "Bengaluru, KA",
      "timestamp": "2024-05-18T16:30:00Z"
    },
    {
      "status": "label_generated",
      "description": "Shipping label created.",
      "location": null,
      "timestamp": "2024-05-18T14:30:00Z"
    }
  ]
}

Normalized Statuses

Every event maps to one of the following normalized statuses:

• created: The shipment exists in RC:Ship but is not yet manifested.
• label_generated: The carrier has accepted the shipment and provided a label.
• picked_up: The carrier has physical possession of the package.
• in_transit: The package is moving through the carrier network.
• out_for_delivery: The package is on the final delivery vehicle.
• delivered: The package was successfully delivered.
• exception: An issue occurred (e.g., weather delay, address not found).