# TCI Express Tracking API & MCP

URL: https://docs.lastscanned.com/carriers/tciexpress

Query live **TCI Express** (`tciexpress`) package status and scan history in a single synchronous `GET` request or MCP tool call. Pass `?carrier=tciexpress` (or the MCP `carrier` argument) so the lookup goes to TCI Express.

## Overview & Quick Facts

| Property | Value |
|---|---|
| **Carrier slug (`?carrier=`)** | `tciexpress` |
| **Brand aliases** | TCI Express, TCI, Transport Corporation of India Express, tciexpress.in |
| **Category** | Regional (express parcel and surface cargo, India) |
| **Single-package REST endpoint** | `GET https://api.lastscanned.com/v1/track/{trackingNumber}` |
| **Batch REST endpoint** | `GET https://api.lastscanned.com/v1/track?numbers=829434104,...` |
| **MCP server (`https://mcp.lastscanned.com`)** | `track_package`, `track_packages`, `list_carriers` |
| **Authentication & pricing** | `Authorization: Bearer lsk_live_...` · 1 free keyless lookup/day per IP |

## Tracking Number Formats & Auto-Detection

| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
| **Pass 1 (`matches`)** | none | none | none |
| **Pass 2 (`mayMatch`)** | none | none | none |

Nine- or ten-digit dockets are a shape other carriers also use, so pass `?carrier=tciexpress`. Accepted shape: `^\d{9,10}$`.

## Synchronous `GET` Request & Normalized JSON Response

```bash
curl -s "https://api.lastscanned.com/v1/track/829434104?carrier=tciexpress" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"
```

```json
{
  "carrier": "tciexpress",
  "trackingNumber": "829434104",
  "status": "delivered",
  "statusDescription": "Shipment delivered",
  "service": null,
  "deliveredAt": null,
  "deliveredAtLocal": "2026-03-20",
  "signedBy": null,
  "destination": {
    "city": "PUNE",
    "state": null,
    "country": "IN"
  },
  "events": [
    {
      "timestamp": null,
      "localTime": "2026-03-20",
      "status": "delivered",
      "description": "Shipment delivered",
      "location": null,
      "code": null
    },
    {
      "timestamp": "2026-03-17T08:58:00Z",
      "localTime": "2026-03-17T14:28:00",
      "status": "in_transit",
      "description": "Arrived",
      "location": "XPNH (PUNE HUB)",
      "code": null
    },
    {
      "timestamp": "2026-03-14T17:53:00Z",
      "localTime": "2026-03-14T23:23:00",
      "status": "in_transit",
      "description": "Despatched to XPNH (PUNE HUB)",
      "location": "XDEL (DELHI HUB)",
      "code": null
    },
    {
      "timestamp": null,
      "localTime": "2026-03-12",
      "status": "in_transit",
      "description": "Booked",
      "location": "XJPR (JAIPUR BKG)",
      "code": null
    }
  ]
}
```

## Notes

- **Scans**: the docket page lists the delivery rows, the booking and a hub-to-hub transhipment table. Each transhipment row becomes a `Despatched to …` scan (at the sending hub) and, once it has arrived, an `Arrived` scan (at the receiving hub).
- **Time zone**: India has one offset (+05:30). Delivery and booking rows have a date only, so they carry `localTime` as a date and no `timestamp`.

## Related Resources

- **Regex & check digits**: [Tracking number formats & auto-detection](/formats)