Track Shipment
Copy for LLM
Copy page as Markdown for LLMs
View as Markdown
Open this page as Markdown
Open in ChatGPT
Get insights from ChatGPT
Open in Claude
Get insights from Claude
Connect to Cursor
Install MCP server on Cursor
Connect to VS Code
Install MCP server on VS Code

The Track Shipment API enables real-time tracking of shipment status and location for both forward and return journeys. By providing either a shipment ID or AWB number, you can retrieve comprehensive tracking information including current status, courier details, location data, estimated delivery dates, and a complete history of tracking events from pickup to delivery.

This endpoint is can be used for shipment visibility, monitoring delivery progress, troubleshooting delivery issues, and maintaining transparency throughout the order fulfillment lifecycle.

Use operational_status field to trigger automated order processing workflows or customer notifications on the seller system.

Request Type: POST
Scheme: HTTPS
Endpoint: https://{{host}}/oms/v3/shipment/track

Try out Fynd Konnect's Track Shipment Endpoint

Common Request Headers

Header	Mandatory	Description
`x-access-token`	Yes	Access token used for authenticating API requests to Fynd Konnect
`Content-Type`	Yes	`application/json`

Best Practices

Implement caching: Cache tracking data for 5-10 minutes to reduce API calls for frequent status checks
Parse event history: Extract event timestamps and locations to build visual tracking timelines
Handle missing data: Some fields (ETA, tracking URL) may be null depending on courier capabilities
Display location data: Parse GPS coordinates from location field for map-based tracking interfaces
Track delivery exceptions: Monitor for status codes indicating delivery failures or RTO scenarios

Request Body Schema

shipment_idstring

Unique shipment identifier for forward or return journey (forward_id or return shipment ID from order payload)

awb_numberstring

Air Waybill number assigned by the courier partner

Identifier Requirements

Either shipment_id OR awb_number is mandatory. If both are provided, shipment_id takes priority. At least one identifier must be included for successful tracking.

Success Response

statusstring

API response status (success or error)

dataobject

Shipment tracking information

API Call Example

curl -i -X POST \
  https://fyndkonnect.konnect.uat.fyndx1.de/oms/v3/shipment/track \
  -H 'Content-Type: application/json' \
  -H 'x-access-token: YOUR_API_KEY_HERE' \
  -d '{
    "shipment_id": "string",
    "awb_number": "string"
  }'

Example Response

Tracking response for a forward delivery shipment:

  {
    "status": "success",
    "data": {
      "courier": "fynd-test",
      "current_status": "DL",
      "last_updated": "2025-10-31T13:55:59",
      "eta": null,
      "promised_delivery_date": "2025-11-02T10:00:00",
      "tracking_url": "https://www.fynd.com/",
      "location": "{\"coordinates\":{\"latitude\":19.0369701,\"longitude\":73.0136186}}",
      "shipment_id": "17618887002341430000",
      "awb_number": "FY12345",
      "operational_status": "delivery_done",
      "journey": "forward",
      "events": [
        {
          "id": 107134246,
          "status": "DL",
          "operational_status": "delivery_done",
          "location": "{\"coordinates\":{\"latitude\":19.0369701,\"longitude\":73.0136186}}",
          "timestamp": "2025-10-31T13:55:59",
          "remarks": "Shipment has been delivered"
        },
        {
          "id": 107130550,
          "status": "OFD",
          "operational_status": "out_for_delivery",
          "location": "{\"coordinates\":{\"latitude\":19.0210483,\"longitude\":73.0183319}}",
          "timestamp": "2025-10-31T13:26:08",
          "remarks": "Driver is out for delivery"
        },
        {
          "id": 107130422,
          "status": "SL",
          "operational_status": "bag_picked",
          "location": "{\"coordinates\":{\"latitude\":19.021045,\"longitude\":73.0183328}}",
          "timestamp": "2025-10-31T13:24:57",
          "remarks": "Driver has picked the shipment"
        },
        {
          "id": 107130254,
          "status": "OFP",
          "operational_status": "bag_not_picked",
          "location": "{\"coordinates\":{\"latitude\":19.0210448,\"longitude\":73.0183157}}",
          "timestamp": "2025-10-31T13:23:26",
          "remarks": "Driver is out for picking the shipment"
        },
        {
          "id": 107126205,
          "status": "TA",
          "operational_status": "bag_not_picked",
          "location": null,
          "timestamp": "2025-10-31T12:51:01",
          "remarks": "Trip has been assigned and waiting for rider"
        }
      ],
      "meta": {
        "remark": "Shipment has been delivered",
        "courier_partner_shipper_name": "fynd-test"
      }
    }
  }

Understanding Operational Statuses

The events array records a time-ordered trail of the shipment’s journey, with each entry capturing a key milestone or status update.

Status	Description
`handed_over_to_dg`	Bag handed over to delivery gateway partner by the store/WH staff
`bag_not_picked`	Bag was not picked up by the delivery partner from the store/WH
`out_for_pickup`	Bag is scheduled for pickup by delivery personnel
`bag_picked`	Delivery partner successfully picked up the bag from the store
`dp_reached_pickup_point`	Delivery partner arrived at the pickup point
`bag_not_handed_over_to_dg`	Store did not hand over bag to DG; pre-pickup issue
`out_for_delivery`	Bag is en route to customer
`delivery_attempt_failed`	Attempted but failed delivery (e.g., customer unavailable)
`delivery_reattempt_requested`	System or ops triggered a reattempt of delivery
`delivery_done`	Successful delivery to customer
`handed_over_to_customer`	Another terminal handover state confirming customer receipt
`in_transit`	General “on the way” transit phase (mid-journey)
`bag_reached_drop_point`	Bag reached the final drop node but not yet delivered
`rto_initiated`	Return-to-origin triggered
`rto_in_transit`	RTO package in transit back to the store
`rto_bag_out_for_delivery`	RTO bag on route to merchant
`rto_bag_delivered`	RTO bag successfully delivered back
`rto_bag_accepted`	RTO bag accepted by merchant/store
`return_dp_out_for_pickup`	Return delivery partner dispatched for pickup
`return_bag_in_transit`	Return bag moving between customer → warehouse → store
`return_bag_out_for_delivery`	Return bag is en route to destination
`return_bag_delivered`	Return bag delivered back to store/merchant
`return_dp_reached_pickup_point`	Return delivery partner reached customer location
`return_bag_reached_drop_point`	Return bag reached return hub/drop point

Location Data Format

The location field contains GPS coordinates in JSON string format. Parse this to extract latitude and longitude:

{
  "coordinates": {
    "latitude": 19.0369701,
    "longitude": 73.0136186
  }
}

These coordinates can be used to:

Display shipment location on maps
Calculate distance from destination
Show proximity-based delivery estimates
Build visual tracking interfaces

Track ShipmentCopyCopy for LLMCopy page as Markdown for LLMsView as MarkdownOpen this page as MarkdownOpen in ChatGPTGet insights from ChatGPTOpen in ClaudeGet insights from ClaudeConnect to CursorInstall MCP server on CursorConnect to VS CodeInstall MCP server on VS Code