Track Professional Courier Shipments via API

Why track The Professional Couriers shipments through an API

Tracking updates for The Professional Couriers consignments are logged across branch offices and regional sorting facilities. Employing a professional courier tracking api integration provides structured visibility across these checkpoints while normalizing regional status descriptions into standard stages.

Raw tracking scan descriptions frequently emit unspaced keyword concatenations (such as outfordelivery), regional dispatch phrasing (such as Despatched to HYDERABAD), and British English spelling variations. ClearTrack normalizes these tokens before running stage classification rules.

Additionally, when same-day scans arrive with varied sequence indices, ClearTrack sorts events chronologically by timestamp so downstream systems always receive milestones in verified chronological order.

Request example

Pass any valid Professional Courier consignment code to the API endpoint with your active authorization header:

          cURL
          GET /v1/track/professional/:awb
        

curl -s -H "X-API-Key: ct_live_your_api_key" \
  "https://api.cleartrackpromise.in/v1/track/professional/NLM60580328"

Real response

The following payload displays an authentic production shipment currently out for delivery with stuck status flags derived from transit scan intervals:

          JSON (Verified Production Response)
          200 OK
        

{
  "awb": "NLM***328",
  "tracking_number": "NLM***328",
  "carrier": "professional",
  "status": "out_for_delivery",
  "status_text": "Out for Delivery",
  "is_delivered": false,
  "is_rto": false,
  "origin": null,
  "destination": null,
  "estimated_delivery_at": null,
  "delivered_at": null,
  "first_scan_at": "2026-09-23T12:15:00.000Z",
  "last_location": "Bengaluru",
  "last_known_location": "Bengaluru",
  "last_updated_at": "2026-10-14T08:08:48.491Z",
  "last_polled_at": "2026-10-14T08:08:48.491Z",
  "cached": true,
  "stale": false,
  "shipment": {
    "service_type": null,
    "weight_grams": null,
    "origin": null,
    "destination": null,
    "booked_at": null
  },
  "milestones": {
    "booked_at": null,
    "picked_up_at": null,
    "in_transit_at": "2026-09-23T12:15:00.000Z",
    "out_for_delivery_at": "2026-09-24T06:16:00.000Z",
    "first_attempt_at": null,
    "delivered_at": null,
    "rto_initiated_at": null,
    "rto_delivered_at": null
  },
  "delivery_attempts": {
    "count": 0,
    "attempts": []
  },
  "insights": {
    "transit_days_elapsed": 20.8,
    "hours_since_last_scan": 481.9,
    "is_stuck": true,
    "is_late_vs_carrier_edd": null,
    "delay_days_vs_carrier_edd": null,
    "hub_count": 2,
    "current_stage": "out_for_delivery",
    "requires_attention": true,
    "attention_reason": "stuck",
    "benchmark": {
      "median_transit_days_for_route": null,
      "sample_size": null,
      "expected_delivery_by": null
    }
  },
  "events": [
    {
      "timestamp": "2026-09-24T06:16:00.000Z",
      "status": "out_for_delivery",
      "status_text": "outfordelivery: Out for Delivery - Area : [REDACTED]",
      "code": "out_for_delivery",
      "facility": "Bengaluru",
      "location": "Bengaluru",
      "description": "outfordelivery: Out for Delivery - Area : [REDACTED]"
    },
    {
      "timestamp": "2026-09-24T05:39:00.000Z",
      "status": "in_transit",
      "status_text": "intransit: Received at BENGALURU-HGR",
      "code": "dispatched",
      "facility": "Bengaluru",
      "location": "Bengaluru",
      "description": "intransit: Received at BENGALURU-HGR"
    },
    {
      "timestamp": "2026-09-24T04:40:00.000Z",
      "status": "in_transit",
      "status_text": "intransit: Despatched to NELAMANGALA-HGR",
      "code": "dispatched",
      "facility": "Nelamangala",
      "location": "Nelamangala",
      "description": "intransit: Despatched to NELAMANGALA-HGR"
    },
    {
      "timestamp": "2026-09-23T12:15:00.000Z",
      "status": "in_transit",
      "status_text": "intransit: Despatched to BENGALURU-NLM",
      "code": "dispatched",
      "facility": "Bengaluru",
      "location": "Bengaluru",
      "description": "intransit: Despatched to BENGALURU-NLM"
    }
  ]
}

The Professional Couriers status mapping

Generic normalization applied to real status strings observed across branch networks:

Raw Branch Event Text	ClearTrack `status`	ClearTrack `current_stage`	Lifecycle Meaning
`outfordelivery: Out for Delivery - Area : ...`	`out_for_delivery`	`out_for_delivery`	Unspaced token normalized; package out on local branch delivery van.
`delivered: Delivered - Area : ...`	`delivered`	`delivered`	Confirmed delivery recorded by destination branch office; terminal state.
`intransit: Despatched to [Hub]`	`in_transit`	`in_transit`	Forwarded along transit line-haul to designated destination or hub.
`intransit: Received at [Hub]`	`in_transit`	`in_transit`	Inbound sorting scan verified at transshipment center or city office.
`intransit: Bag Despatched to [Hub]`	`in_transit`	`in_transit`	Consolidated manifest container dispatched between regional hubs.
`Address Improper - Area : ...`	`delivery_attempted`	`delivery_attempted`	Attempt failed due to incomplete address; logged with NDR code `incomplete_address`.

Delivery insights for The Professional Couriers

Automated operational diagnostics derived for each Professional Courier consignment:

Stuck Detection

is_stuck: true highlights consignments where more than 72 hours have passed without an updated branch scan while the parcel remains in an active stage.

Elapsed Transit Duration

transit_days_elapsed measures journey duration from the first branch scan — pre-pickup delays aren't included.

Scan Inactivity

hours_since_last_scan monitors hours since the latest branch event, isolating intermediate transit delays.

Route-level median transit duration benchmarks activate dynamically once a specific courier lane records 30 or more delivered shipments in the ClearTrack network.

Carrier-specific notes

Normalization of concatenated status keywords

Branch scan feeds frequently emit unspaced tokens like "outfordelivery" and spelling variations like "Despatched". ClearTrack applies word boundary stripping and phonetic normalization to map these legacy strings into standard stages.

Deterministic chronological checkpoint sorting

Because branch checkpoints are logged from decentralized physical centers, same-day events can arrive out of order. ClearTrack sorts and normalizes events chronologically so the latest scan always accurately reflects physical status.

Frequently asked questions

How are lookups priced for The Professional Couriers?

Lookups cost between ~₹0.25 and ₹0.27 each in Indian Rupees under transparent prepaid bundles, with zero auto-renewal mandates or credit card requirements.

Is ClearTrack affiliated with The Professional Couriers?

No. ClearTrack is an independent developer platform and is not affiliated with, endorsed by, or sponsored by The Professional Couriers. All trademarks belong to their respective owners.

Does querying a cached shipment record deduct a lookup?

Yes. Every HTTP request made to the tracking endpoint deducts 1 lookup from your plan allowance, whether cached or live.

How does the API interpret unspaced tracking statuses from The Professional Couriers?

ClearTrack strips spaces and punctuation during event parsing so strings like "outfordelivery" and "Despatched to" normalize deterministically to standard stages like "out_for_delivery" and "in_transit".