Carrier Integration

Ekart Tracking API

Track Ekart Logistics parcels through a normalized REST API with real-time milestone events, delivery attempt categorization, and inactivity alerts.

Get a free API key

cURL Integration Example

Query live consignment tracking data by passing your ClearTrack API key in the X-API-Key request header:

cURL GET /v1/track/ekart/:awb
curl -s -H "X-API-Key: YOUR_API_KEY" \
  "https://api.cleartrackpromise.in/v1/track/ekart/FMPC0000000001"

Sample JSON Response

ClearTrack returns a standardized JSON payload with normalized status enums, milestone timestamps, diagnostic insights, and sanitized checkpoint events:

JSON (Illustrative Example) 200 OK
{
  "awb": "FMPC0000000001",
  "tracking_number": "FMPC0000000001",
  "carrier": "ekart",
  "status": "in_transit",
  "status_text": "In Transit - Dispatched to Delivery Hub",
  "is_delivered": false,
  "is_rto": false,
  "origin": {
    "office": "Bhiwandi Gateway",
    "city": "Thane",
    "state": "Maharashtra",
    "pincode": "421302"
  },
  "destination": {
    "office": "Whitefield Delivery Hub",
    "city": "Bengaluru",
    "state": "Karnataka",
    "pincode": "560066"
  },
  "estimated_delivery_at": "2026-10-18T18:00:00.000Z",
  "delivered_at": null,
  "first_scan_at": "2026-10-15T09:00:00.000Z",
  "last_location": "Bengaluru Sorting Center",
  "last_known_location": "Bengaluru Sorting Center",
  "last_updated_at": "2026-10-16T13:45:00.000Z",
  "last_polled_at": "2026-10-16T13:45:00.000Z",
  "cached": true,
  "stale": false,
  "shipment": {
    "service_type": "standard",
    "weight_grams": 510,
    "origin": {
      "office": "Bhiwandi Gateway",
      "city": "Thane",
      "state": "Maharashtra",
      "pincode": "421302"
    },
    "destination": {
      "office": "Whitefield Delivery Hub",
      "city": "Bengaluru",
      "state": "Karnataka",
      "pincode": "560066"
    },
    "booked_at": "2026-10-15T09:00:00.000Z"
  },
  "milestones": {
    "booked_at": "2026-10-15T09:00:00.000Z",
    "picked_up_at": "2026-10-15T10:15:00.000Z",
    "in_transit_at": "2026-10-15T13:00:00.000Z",
    "out_for_delivery_at": null,
    "first_attempt_at": null,
    "delivered_at": null,
    "rto_initiated_at": null,
    "rto_delivered_at": null
  },
  "delivery_attempts": {
    "count": 0,
    "attempts": []
  },
  "insights": {
    "transit_days_elapsed": 1.2,
    "hours_since_last_scan": 2.5,
    "is_stuck": false,
    "is_late_vs_carrier_edd": false,
    "delay_days_vs_carrier_edd": null,
    "hub_count": 2,
    "current_stage": "in_transit",
    "requires_attention": false,
    "attention_reason": null,
    "benchmark": {
      "median_transit_days_for_route": null,
      "sample_size": null,
      "expected_delivery_by": null
    }
  },
  "events": [
    {
      "timestamp": "2026-10-16T13:45:00.000Z",
      "status": "in_transit",
      "status_text": "Item Dispatched to Delivery Hub",
      "code": "dispatched",
      "facility": "Bengaluru Sorting Center",
      "location": "Bengaluru",
      "description": "Item Dispatched to Delivery Hub"
    },
    {
      "timestamp": "2026-10-15T10:15:00.000Z",
      "status": "picked_up",
      "status_text": "Shipment Handed Over to Ekart",
      "code": "picked_up",
      "facility": "Bhiwandi Gateway",
      "location": "Thane",
      "description": "Shipment Handed Over to Ekart"
    }
  ]
}

Status Mapping: Ekart to Normalized Status

Raw status updates and checkpoint descriptions emitted by Ekart are mapped into standardized top-level status values and granular code identifiers:

Carrier Raw Status Normalized Status (status) Event Code (code) Description
Approved / Order Placed order_placed booked Order record confirmed in merchant system; pending packaging and pickup.
Packed / Awaiting Pickup awaiting_pickup booked Package packed and manifested; awaiting physical collection by Ekart courier.
Shipped / In Transit shipped dispatched Consignment handed over to Ekart and in movement between transit hubs.
Arrived at Hub / Inscan in_transit received Package received and scanned at destination or transshipment facility.
Out for Delivery out_for_delivery out_for_delivery Package loaded onto delivery vehicle with executive for doorstep attempt.
Delivered delivered delivered Package successfully handed over to recipient (terminal state).
Delivery Attempt Failed returned delivery_attempted Delivery attempted but failed due to customer unavailable, door locked, or address issue.
RTO Initiated / Return Started returned rto_initiated Undelivered shipment initiated for reverse movement back to seller origin.

For the comprehensive lifecycle specification across all couriers, see the Shipment Statuses Reference.

Non-Delivery Report (NDR) Reasons

When delivery attempts fail, ClearTrack normalizes unstructured failure remarks into canonical NDR reason codes inside the delivery_attempts array:

Normalized Reason Code Diagnostic Category Meaning
customer_unavailable Customer Unavailable Recipient absent from delivery address, phone unreachable, or rescheduled.
address_issue Address Issue Incomplete address, missing landmark, incorrect house number, or invalid pin code.
refused Customer Refused Recipient refused to accept package or rejected delivery verification.
premises_closed Premises Closed Commercial office, shop, or residential premises closed at delivery attempt.
cod_not_ready COD Payment Not Ready Cash on delivery payment not ready or digital doorstep collection failed.
other Operational Exception Carrier operational constraint, route delay, or weather hold.

Learn how to automate buyer re-attempt outreach in our NDR Reason Codes Documentation.

AWB Format

Ekart tracking numbers are 14-character alphanumeric identifiers typically starting with a 4-letter prefix such as FMPC, FMPP, FDSP, or CLQC followed by 10 digits (for example, FMPC0000000001). Pass the 14-character ID directly into the :awb path parameter.

Frequently Asked Questions

Does Ekart have an official tracking API?

Ekart Logistics serves as the dedicated logistics and fulfillment arm for Flipkart and contracted enterprise partners. Public self-serve tracking APIs are not generally offered to non-contracted developers. ClearTrack allows developers to track Ekart consignments via a unified REST JSON API without requiring an enterprise contract with Ekart or Flipkart.

Do I need an Ekart account to use ClearTrack?

No. You do not need an Ekart commercial account, merchant relationship, or Flipkart login credentials. ClearTrack handles tracking requests through your ClearTrack API key.

How fresh is the tracking data?

Active in-transit consignments are cached for up to 30 minutes, ensuring high performance while adhering to upstream limits. Terminal states (delivered, returned, and cancelled) are cached permanently.

What does the tracking API cost?

Pricing is pay-as-you-go based on lookups in Indian Rupees (₹), ranging from ₹0.25 to ₹0.27 per lookup across prepaid plans with no recurring mandates. We offer a free 14-day trial with 100 lookups for business accounts. View our full pricing plans on the pricing page.

Can I track Ekart alongside other couriers in the same integration?

Yes. ClearTrack provides an identical JSON response schema across all supported carriers, so your application parses Ekart, Delhivery, Blue Dart, and India Post using the exact same code.

Prepaid Pricing in Indian Rupees (₹)

Simple prepaid lookup packs with no monthly auto-debit mandates, no foreign currency conversion fees, and no contract lock-ins:

Free Trial
₹0
100 lookups / 14 days
Starter
₹399
1,500 lookups (~₹0.27/call)
Growth
₹999
4,000 lookups (~₹0.25/call)
Business
₹3,000
12,000 lookups (₹0.25/call)
View Full Pricing Details Start Free Trial

Supported Logistics Networks

Track other Indian parcel couriers using the same unified JSON API format:

Delhivery
Surface & air express parcels pan-India
Blue Dart
Express air & surface logistics network
Speed Post
Domestic express postal delivery network
India Post
Postal tracking across all pincodes

For a multi-carrier integration overview, read our guide to the Shipment Tracking API in India.

ClearTrack is not affiliated with, endorsed by, or sponsored by any courier company. All trademarks belong to their respective owners.