DHLink Tracking API & MCP
Query live DHLink (dhlink) package status and scan history in a single synchronous GET request or MCP tool call.
dhlink covers DHLink, a consolidator that ships e-commerce parcels from China to the US, UK and elsewhere. Its numbers start FC and it also tracks the postal numbers it carries.
Source: Plain POST https://www.dhlink.com/stage-api/trbiz/track/queryTrack, no key needed.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | dhlink |
| Brand aliases | DHLink, DHL ink, FC tracking, cross-border e-commerce China |
| Category | Cross-border e-commerce parcels |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber}?carrier=dhlink |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=...,...&carrier=dhlink |
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 |
FC + 13 digits is not claimed by auto-detection, so pass ?carrier=dhlink. S10 postal numbers (XX123456785CN) belong to the postal operators.
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/FC2400000000000?carrier=dhlink" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"{
"carrier": "dhlink",
"trackingNumber": "FC2400000000000",
"status": "delivered",
"statusDescription": "Delivered",
"service": null,
"deliveredAt": null,
"deliveredAtLocal": "2024-05-04T16:07:00",
"signedBy": null,
"destination": {
"city": null,
"state": null,
"country": "US"
},
"events": [
{
"timestamp": null,
"localTime": "2024-05-04T16:07:00",
"status": "delivered",
"description": "Delivered",
"location": "WASHINGTON, DC 20024",
"code": null
},
{
"timestamp": null,
"localTime": "2024-05-04T06:18:00",
"status": "out_for_delivery",
"description": "WASHINGTON, DC, US 20024, Out for Delivery, Expected Delivery by 7:40pm",
"location": "WASHINGTON, DC, US 20024",
"code": null
},
{
"timestamp": null,
"localTime": "2024-04-30T11:42:00",
"status": "in_transit",
"description": "MANASSAS, VA 20109, Arrived Shipping Partner Facility, USPS Awaiting Item",
"location": "MANASSAS, VA 20109",
"code": null
}
]
}Notes
- Scans: DHLink merges the origin post's, the destination carrier's and its own scans, often twice or in Chinese. Chinese-only lines and duplicates are dropped and the source with the most scans is kept, so
descriptionis the carrier's English wording, which sometimes repeats the place. - Time zone: scan times carry no zone, so only
localTimeis set.
Related Resources
- Regex & check digits: Tracking number formats & auto-detection
DHL Freight Tracking API & MCP
Track DHL Freight (ActiveTracing) road freight consignments via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.
XQ Express Tracking API & MCP
Track XQ Express (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.