Carriers

Delhivery Tracking API & MCP

Query live Delhivery (delhivery) package status and scan history in a single synchronous GET request or MCP tool call, using the same public JSON that Delhivery's own tracking page calls. Pass ?carrier=delhivery for its plain 13- and 14-digit waybills.

Overview & Quick Facts

PropertyValue
Carrier slug (?carrier=)delhivery
Brand & service aliasesDelhivery, Delhivery Express, Delhivery Courier, Delhivery AWB
CategoryIndia domestic parcel & e-commerce
Single-package REST endpointGET https://api.lastscanned.com/v1/track/{trackingNumber}?carrier=delhivery
Batch REST endpointGET https://api.lastscanned.com/v1/track?numbers=1234567890123,1234567890123&carrier=delhivery
MCP server (https://mcp.lastscanned.com)track_package, track_packages, list_carriers (claude mcp add --transport http lastscanned https://mcp.lastscanned.com)
Authentication & pricingAuthorization: Bearer lsk_live_... · 1 free keyless lookup/day per IP · Free tier (5 unique numbers/day, $0) · Pro ($4.99/mo for 1,000 unique numbers, unlimited re-polls, $0.015/extra) · HTTP 402 Stripe MPP ($0.50 for 25-number lsk_pack_ key or $0.02/number in USDC on Tempo)

Tracking Number Formats & Auto-Detection (matches vs ?carrier=delhivery)

PassRule / RegexCheck DigitExamples
Pass 1 (matches)None——
Pass 2 (mayMatch)/^\d{13,14}$/—1234567890123
Explicit (?carrier=delhivery)Any Delhivery waybill (AWB)—1234567890123

When is ?carrier=delhivery optional vs required?

  • Optional: a 13- or 14-digit number that no other carrier claims is tried against Delhivery in Pass 2.
  • Recommended: pass ?carrier=delhivery anyway, because plain digit runs are not Delhivery's alone.

Synchronous GET Request & Normalized JSON Response

curl -s "https://api.lastscanned.com/v1/track/1234567890123?carrier=delhivery" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"
const res = await fetch("https://api.lastscanned.com/v1/track/1234567890123?carrier=delhivery", {
  headers: { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` },
});
const pkg = await res.json();
console.log(pkg.status, pkg.events[0]);

MCP track_package tool call:

{
  "tool": "track_package",
  "arguments": { "tracking_number": "1234567890123", "carrier": "delhivery" }
}

Normalized TrackingResult response:

{
  "carrier": "delhivery",
  "trackingNumber": "1234567890123",
  "status": "in_transit",
  "statusDescription": "Shipment received at facility",
  "service": null,
  "deliveredAt": null,
  "deliveredAtLocal": null,
  "signedBy": null,
  "destination": null,
  "events": [
    {
      "timestamp": "2026-10-25T08:07:38Z",
      "localTime": "2026-10-25T13:37:38",
      "status": "in_transit",
      "description": "Shipment received at facility",
      "location": "Bengaluru_Bidadi_H (Karnataka)",
      "code": "UD"
    },
    {
      "timestamp": "2026-10-24T11:20:00Z",
      "localTime": "2026-10-24T16:50:00",
      "status": "label_created",
      "description": "Manifested",
      "location": "Mumbai_Bhiwandi_H (Maharashtra)",
      "code": "X-UCI"
    }
  ]
}

Notes

  • Source: the unified-tracking JSON behind Delhivery's own tracking page, no account or key. A number Delhivery does not know ("invalid AWB or very old package") returns not_found.
  • Times: Delhivery prints India Standard Time with no offset. India is one zone, so each event carries timestamp in UTC computed from Asia/Kolkata.
  • Old waybills: Delhivery drops tracking for very old packages, which then read as not_found.

Yamato Transport (Kuroneko Yamato / ヤマト運輸) Tracking API & MCP

Track Yamato Transport (Kuroneko Yamato, TA-Q-BIN, ヤマト運輸) parcels in Japan via synchronous REST GET or MCP. Normalized JSON status and scan history with Asia/Tokyo timestamps, no carrier credentials required.

Blue Dart (DHL Group, India) Tracking API & MCP

Track Blue Dart (DHL Group, India) shipments via synchronous REST GET or MCP. Normalized JSON status and scan history with Asia/Kolkata timestamps, no carrier credentials required.

On this page

Overview & Quick FactsTracking Number Formats & Auto-Detection (matches vs ?carrier=delhivery)When is ?carrier=delhivery optional vs required?Synchronous GET Request & Normalized JSON ResponseNotesRelated Resources