Carriers
ESHUN (ZES Express) Tracking API & MCP
Query live ESHUN / ZES Express (eshun) package status, scan history, and the last-mile order number in a single synchronous GET request or MCP tool call. lastscanned auto-detects ZES…YQ numbers.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | eshun |
| Brand aliases | ESHUN, ZES Express, 俄顺物流, 俄顺国际物流 |
| Category | Cross-border (China to Russia) |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber} |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=ZES...,ZES... |
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) | /^ZES[A-Z]{2}\d{10}YQ$/ | none | ZESAB1234567890YQ |
Pass 2 (mayMatch) | none | none | none |
ZES numbers belong to ESHUN alone, so ?carrier=eshun is optional.
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/ZESAB1234567890YQ" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"{
"carrier": "eshun",
"trackingNumber": "ZESAB1234567890YQ",
"status": "delivered",
"statusDescription": "结案",
"service": null,
"deliveredAt": null,
"deliveredAtLocal": "2026-03-14T15:25:10",
"signedBy": null,
"destination": { "city": null, "state": null, "country": "RU" },
"message": "Handed to the destination carrier as 71234567890123",
"events": [
{
"timestamp": null,
"localTime": "2026-03-14T15:25:10",
"status": "delivered",
"description": "结案",
"location": null,
"code": null
},
{
"timestamp": null,
"localTime": "2026-03-13T03:15:00",
"status": "out_for_delivery",
"description": "到达待取",
"location": null,
"code": null
},
{
"timestamp": null,
"localTime": "2026-03-12T23:11:54",
"status": "in_transit",
"description": "транзит",
"location": null,
"code": null
}
]
}Notes
- Handoff:
messagecarries the Russian last-mile order number (the page's "渠道转单号"). The page does not name the delivery company. - Language: scan text is Chinese or Russian, as the carrier prints it.
- Source: ESHUN's tracking runs on a rtb56 server reached by IP address. The lookup asks its JSON web service (one call for a whole batch), falls back to the tracker page (whose slider check the server accepts with a wide error margin), and last to a browser session on that page.
- Statuses: ESHUN's own codes are mapped:
CCdelivered,DQwaiting for pickup,NT/ND/NO/NCin transit.codeholds the scan's event code. - Time zone: scans made in China carry
+08:00and get atimestamp; scans in Russia have no zone and keep onlylocalTime.
Related Resources
- Regex & check digits: Tracking number formats & auto-detection
Yincag Logistics Tracking API & MCP
Track Yincag Logistics (云仓国际, cross-border parcels from China, Hualei tracker) with scan history via synchronous REST GET or MCP. Normalized JSON status and scans, no carrier credentials required.
ACS Courier Tracking API & MCP
Track ACS Courier parcels via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.