UapiProUApiPro
Misc

Track Express Shipments

0calls
40 credits / call

Want to know where your package is right now? This endpoint returns real-time tracking history.

GET
uapis.cn
/api/v1/misc/tracking/query
Query parameters
4
tracking_number
string
required

Tracking number. Usually a 10–20 digit alphanumeric string.

carrier_code
string

Carrier code (optional). When omitted, the endpoint auto-detects the carrier; specifying the code makes the lookup faster.

refresh
boolean

Whether to fetch the latest tracking information again.

phone
string
Pro

Last 4 digits of the recipient phone number (optional). Some carriers require this to return detailed tracking information.

Overview

Given a tracking number, the endpoint auto-detects the carrier and returns the full tracking history. Major Chinese carriers — ZTO, YTO, Yunda, STO, J&T, SF Express, JD Logistics, EMS, Deppon — are supported.

Usage notes

  • Auto-detect: If you do not know the carrier, the endpoint detects it from the tracking-number format (recommended).
  • Manual override: If you already know the carrier, pass carrier_code for a faster lookup.
  • Phone verification: Some carriers (e.g. SF Express) require the recipient phone-number suffix to return detailed tracking. If you receive No tracking information available, retry with the phone parameter.
  • Latency: Tracking is fetched in real time and typically responds within 1–2 seconds.

Query parameters

tracking_number
stringrequired

Tracking number. Usually a 10–20 digit alphanumeric string.

carrier_code
stringoptional

Carrier code (optional). When omitted, the endpoint auto-detects the carrier; specifying the code makes the lookup faster.

phone
stringoptional

Last 4 digits of the recipient phone number (optional). Some carriers require this to return detailed tracking information.

refresh
booleanoptional

Whether to fetch the latest tracking information again.

Response

200 / OK

Success. Returns the full tracking history for the package.

JSON
{
  // Tracking number.
  "tracking_number": "YT1234567890123",
  // Carrier code.
  "carrier_code": "yuantong",
  // Carrier name.
  "carrier_name": "圆通速递",
  // Number of tracking events.
  "track_count": 3,
  // Tracking history, in reverse-chronological order.
  "tracks": [
    {
      // Tracking-event timestamp.
      "time": "2025-10-27 15:30:00",
      // Tracking-event description.
      "context": "Package signed for. Thank you for using YTO Express."
    }
  ]
}

400 / Bad Request

Invalid parameter. Verify the tracking number.

JSON
{
  "code": "INVALID_ARGUMENT",
  "message": "Missing tracking_number parameter"
}

404 / Not Found

Returned with status 404 when no tracking history is available. If you receive this error, retry with the phone parameter (recipient phone-number suffix).

JSON
{
  "code": "NO_TRACKING_DATA",
  "message": "No tracking information available"
}
PreviousProgrammer Historical Events
NextDetect Carrier From Tracking Number