Yurtiçi Kargo (yurtici)→DHL Express / Global (dhl)

Track Yurtiçi Kargo 12-digit Turkish domestic and international outbound shipments.

Yurtiçi Kargo is Turkey’s largest express parcel network, handling domestic Turkish e-commerce fulfillment and international outbound/inbound handoffs with European and global express partners.

Barcode transition: Yurtiçi Kargo to DHL Express / Global

Domestic Yurtiçi Kargo parcels keep the same 92… / 420… barcode from pickup to mailbox. Pass ?carrier=yurtici to inspect middle-mile sort scans before USPS induction.

Yurtiçi Kargo lookup →DHL Express / Global lookup →Format & check-digit detector →
Origin / middle-mile carrier
Yurtiçi Kargo (yurtici)
Yurtiçi Kargo 12-digit shipment code
^\d{12}$
Origin example
109876543210
Final-mile carrier
DHL Express / Global (dhl)
DHL 10-digit waybill or partner barcode
^\d{10}$
Final-mile example
1234567890
Middle-mile resolution
International partner handoff

How the Yurtiçi → DHL handoff works

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

1. Turkish branch pickup (Çıkış Birimi)
Yurtiçi Kargo scans the 12-digit barcode at the origin branch in Istanbul, Ankara, Izmir, or Bursa.
2. Regional transfer center (Aktarma Merkezi)
The parcel moves through Yurtiçi’s automated sortation hubs.
3. Delivery (Teslim Edildi) or international export
Domestic parcels are delivered by the destination Teslim Birimi, while export parcels transfer to international air express.
Yurtiçi query
GET /v1/track/{12_digit_number}?carrier=yurtici
Why ?carrier=yurtici is needed
12-digit numeric barcodes overlap with FedEx Express, so pass ?carrier=yurtici
Normalized status
Maps Turkish scan statuses (Teslim Edildi, Dağıtıma Çıktı, Yolda) to standard English enums

Chain Yurtiçi → DHL in code or MCP

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

Get an API keyWISMO agent guide

REST (Synchronous GET)

# 1. Query Yurtiçi Kargo middle-mile scans on the 92… barcode:
curl "https://api.lastscanned.com/v1/track/109876543210?carrier=yurtici" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

# 2. Query USPS final-mile scans on the same barcode:
curl "https://api.lastscanned.com/v1/track/1234567890" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

TypeScript (Automatic Handoff Chaining)

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

// If USPS is still waiting on the consolidator parcel, query Yurtiçi Kargo middle-mile hubs:
if (pkg.carrier === "usps" && pkg.status === "label_created" && /^(420\d{5})?9[2345]/.test(number)) {
  const mid = await fetch(`https://api.lastscanned.com/v1/track/${encodeURIComponent(number)}?carrier=yurtici`, { headers });
  if (mid.ok) pkg = await mid.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"

Yurtiçi Kargo (Turkey) to DHL International Handoff Tracking FAQ

Why does a 12-digit Yurtiçi Kargo number default to FedEx without ?carrier=yurtici?
FedEx Express also uses 12-digit numeric barcodes. Passing ?carrier=yurtici tells lastscanned to query Yurtiçi Kargo directly.
How does lastscanned normalize Turkish scan events from Yurtiçi Kargo?
lastscanned maps Yurtiçi’s statuses into the standard 7-value status enum (in_transit, out_for_delivery, delivered, exception) while preserving the exact Turkish description and city name.

Other carrier handoff guides

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

"USPS Currently Awaiting Package" 92… Checker →Tracking Number Format & Check-Digit Detector →

All 125 supported carriers

Major carriers

Regional and last mile

International posts and couriers

Cross-border