Resolve YunExpress YT… tracking numbers into SpeedX (SPX…) or GOFO Express (GFUS…) last-mile barcodes in one API call.

When YunExpress flies cross-border parcels into JFK, EWR, ORD, LAX, or MIA for SHEIN, Temu, and TikTok Shop, high-density metro ZIP codes are routed to SpeedX (SPX…) or GOFO Express (GFUS…) instead of USPS. Querying your YT… number on lastscanned returns the exact last-mile SpeedX or GOFO tracking number in the top-level message field.

Try a live tracking number:

Barcode transition: YunExpress to SpeedX / GOFO

When YunExpress clears customs and hands off to SpeedX / GOFO, lastscanned surfaces the secondary tracking number in the top-level message field.

Origin / middle-mile carrier
YunExpress (yunexpress)
YunExpress 18-character YT… waybill
^YT\d{16}$
Origin example
YT2408121234567890
Final-mile carrier
SpeedX / GOFO (speedx)
SpeedX SPX… or GOFO GFUS… barcode
^(SPX|GFUS)[A-Z0-9]{10,18}$
Final-mile example
GFUS01074503026309
Extracted in .message
Delivered by SpeedX (SPXCN0192837465)

How the YunExpress → SpeedX handoff works

Follow the parcel across both networks without waiting on asynchronous webhooks or losing visibility at the handoff boundary.

1. Origin sortation & YT… barcode creation
YunExpress scans the 18-character YT… barcode in Shenzhen, Guangzhou, or Yiwu and assigns the US metro last-mile carrier (SpeedX or GOFO) before departure.
2. Air linehaul & JFK / ORD / LAX customs clearance
The shipment clears CBP Type 86 entry at the destination US airport gateway.
3. SpeedX / GOFO sort center induction
The parcel transfers to SpeedX’s Jamaica NY / Elk Grove Village IL / Compton CA sort facility (or GOFO’s regional hub) and goes out for driver delivery.
Step 1 — Query YunExpress
GET /v1/track/YT2408121234567890 → returns message: "Delivered by SpeedX (SPX...)"
Step 2 — Query SpeedX / GOFO
GET /v1/track/SPX... or GET /v1/track/GFUS01074503026309
Zero webhook delay
Both calls execute synchronously with normalized status enums

Chain YunExpress → SpeedX in code or MCP

Resolve both legs synchronously in TypeScript, curl, or your AI support agent via Streamable HTTP MCP.

REST (Synchronous GET)

# 1. Query YunExpress origin waybill (extracts final-mile barcode in .message):
curl "https://api.lastscanned.com/v1/track/YT2408121234567890" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

# 2. Query the extracted SpeedX / GOFO barcode:
curl "https://api.lastscanned.com/v1/track/GFUS01074503026309" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

TypeScript (Automatic Handoff Chaining)

const headers = { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` };
const originRes = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(number)}`, { headers });
const originPkg = await originRes.json();

// Extract secondary barcode from top-level message ("Delivered by SpeedX (SPXCN0192837465)")
const handoff = originPkg.message?.match(/^Handed to (.+?) as ([A-Z0-9-]+)$/i);
if (handoff) {
  const [, , lastMileNumber] = handoff;
  const destRes = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(lastMileNumber)}`, { headers });
  const destPkg = await destRes.json();
}

Remote MCP (Claude Code / Cursor / ChatGPT)

claude mcp add --transport http lastscanned https://mcp.lastscanned.com \
  --header "Authorization: Bearer lsk_live_YOUR_API_KEY"

YunExpress (YT…) to SpeedX & GOFO Express US Metro Last-Mile Handoff Tracking FAQ

How do I find my SpeedX tracking number from a YunExpress YT… number?
Query your YT… number on lastscanned—the response includes the assigned SpeedX (SPX…) or GOFO (GFUS…) last-mile tracking number in the top-level message field as soon as YunExpress allocates the final-mile label.
Why did YunExpress hand my package to SpeedX instead of USPS?
In high-density metro areas across the Northeast, Midwest, Florida, Texas, and California, cross-border consolidators use SpeedX and GOFO Express for faster 7-day-a-week residential delivery.

Other carrier handoff guides

Explore cross-border last-mile barcode extraction and domestic USPS consolidator overrides across all 273 carriers.

All 273 supported carriers

International posts and couriers

Cross-border