Yamato Transport (Kuroneko Yamato / ヤマト運輸) Tracking API & MCP
Query live Yamato Transport (yamato, クロネコヤマト / TA-Q-BIN) package status and scan history in a single synchronous GET request or MCP tool call. Up to 10 numbers go out in one request to Yamato's own tracking system. Pass ?carrier=yamato: Yamato's 12-digit invoice numbers share their shape with FedEx.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | yamato |
| Brand & service aliases | Yamato Transport, Kuroneko Yamato, クロネコヤマト, ヤマト運輸, TA-Q-BIN, 宅急便 |
| Category | Japan domestic parcel |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber}?carrier=yamato |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=123456789013,123456789013&carrier=yamato |
MCP server (https://mcp.lastscanned.com) | track_package, track_packages, list_carriers (claude mcp add --transport http lastscanned https://mcp.lastscanned.com) |
| Authentication & pricing | Authorization: Bearer lsk_live_... · 1 free keyless lookup/day per IP · Free tier (5 unique numbers/day, $0) · Pro ($4.99/mo for 1,000 unique numbers, unlimited re-polls, $0.015/extra) · HTTP 402 Stripe MPP ($0.50 for 25-number lsk_pack_ key or $0.02/number in USDC on Tempo) |
Tracking Number Formats & Auto-Detection (matches vs ?carrier=yamato)
| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
Pass 1 (matches) | None | — | — |
Pass 2 (mayMatch) | /^\d{12}$/ where the last digit equals the first 11 digits mod 7 | mod 7 | 123456789013 |
Explicit (?carrier=yamato) | Any Yamato invoice number (伝票番号) | mod 7 | 123456789013 |
When is ?carrier=yamato optional vs required?
- Required: a 12-digit run is also a FedEx shape, which wins auto-detection. Always pass
?carrier=yamatofor Yamato invoice numbers. - Numbers with a wrong check digit come back
not_found(伝票番号誤り).
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/123456789013?carrier=yamato" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"const res = await fetch("https://api.lastscanned.com/v1/track/123456789013?carrier=yamato", {
headers: { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` },
});
const pkg = await res.json();
console.log(pkg.status, pkg.events[0]);MCP track_package tool call:
{
"tool": "track_package",
"arguments": { "tracking_number": "123456789013", "carrier": "yamato" }
}Normalized TrackingResult response:
{
"carrier": "yamato",
"trackingNumber": "123456789013",
"status": "delivered",
"statusDescription": "配達完了",
"service": null,
"deliveredAt": "2026-10-21T02:05:00Z",
"deliveredAtLocal": "2026-10-21T11:05:00",
"signedBy": null,
"destination": null,
"events": [
{
"timestamp": "2026-10-21T02:05:00Z",
"localTime": "2026-10-21T11:05:00",
"status": "delivered",
"description": "配達完了",
"location": "大阪営業所",
"code": null
},
{
"timestamp": "2026-10-20T16:10:00Z",
"localTime": "2026-10-21T01:10:00",
"status": "in_transit",
"description": "発送",
"location": "東京ターミナル",
"code": null
}
]
}Notes
- Source: Yamato's own 荷物お問い合わせシステム (
toi.kuronekoyamato.co.jp), server-rendered HTML read from the page's own markup. No account, key or captcha. - No year on scans: Yamato prints scans as
10/21 15:30, so the year is worked out from today's date (no scan is in the future). - Japanese wording:
descriptionis Yamato's own text;statusis mapped from step names such as 荷物受付 (accepted), 配達中 (out for delivery), 配達完了 (delivered) and 持戻 (brought back). - Times: every scan is in Japan, so each event carries
timestampin UTC computed fromAsia/Tokyo.
Related Resources
- Live browser lookup tool: Track a Yamato Transport package live on lastscanned.com/lookup/yamato
- Carrier hub: All supported carriers
- Regex & check digits: Tracking number formats & auto-detection
- AI support workflows: WISMO AI agents & synchronous tracking
CJ Logistics (CJ Korea Express / 대한통운) Tracking API & MCP
Track CJ Logistics (CJ대한통운) parcels in South Korea via synchronous REST GET or MCP. Normalized JSON status and Korean scan history with Asia/Seoul timestamps, no carrier credentials required.
Delhivery Tracking API & MCP
Track Delhivery (India) parcels via synchronous REST GET or MCP. Normalized JSON status and scan history with Asia/Kolkata timestamps, no carrier credentials required.