Carriers
InPost Tracking API & MCP
Query live InPost (inpost) package status and scan history in a single synchronous GET request or MCP tool call. lastscanned auto-detects InPost's 24-digit parcel numbers and reads InPost's own public tracking endpoint for Poland and the UK.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | inpost |
| Brand & service aliases | InPost, InPost Paczkomat, InPost Kurier, InPost UK, ShipX |
| Category | Regional parcel locker & courier network (Poland, UK) |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber} (auto-detected for 24-digit numbers starting 5 or 6) |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=600000000000000000000001,... |
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=inpost)
| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
Pass 1 (matches) | /^[56]\d{23}$/ (24 digits starting 5 or 6) | None | 600000000000000000000001, 520000012345678901234567 |
Pass 2 (mayMatch) | None | n/a | n/a |
When is ?carrier=inpost optional vs required?
- Optional (auto-detected): 24-digit numbers starting 5 or 6.
- Required (
?carrier=inpost): Any other InPost number shape.
Synchronous GET Request & Normalized JSON Response
curl
curl -s "https://api.lastscanned.com/v1/track/600000000000000000000001" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"JavaScript / TypeScript (fetch)
const res = await fetch("https://api.lastscanned.com/v1/track/600000000000000000000001", {
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": "600000000000000000000001"
}
}Normalized TrackingResult JSON response
{
"carrier": "inpost",
"trackingNumber": "600000000000000000000001",
"status": "in_transit",
"statusDescription": "Parcel in the warehouse.",
"service": "locker standard",
"deliveredAt": null,
"deliveredAtLocal": null,
"signedBy": null,
"destination": null,
"events": [
{
"timestamp": "2026-10-22T07:15:00Z",
"localTime": "2026-10-22T09:15:00",
"status": "in_transit",
"description": "Parcel in the warehouse.",
"location": null,
"code": "adopted_at_source_branch"
},
{
"timestamp": "2026-10-20T08:00:00Z",
"localTime": "2026-10-20T10:00:00",
"status": "label_created",
"description": "Prepared by the Sender.",
"location": null,
"code": "confirmed"
}
]
}Notes
- Uses InPost's public ShipX tracking endpoint (
api-shipx-pl.easypack24.net/v1/tracking/{number}). No account or key is needed. - Event wording is InPost's own English status titles. Event times carry their offset, so
timestampis set. - A parcel waiting in a locker or at a service point is reported as
exception, the same way other carriers' held-for-collection scans are.
Related Resources
- Live browser lookup tool: Track a InPost package live on lastscanned.com/lookup/inpost
- Regex & check digits: Tracking number formats & auto-detection
- AI support workflows: WISMO AI agents & synchronous tracking
GLS Group Europe Tracking API & MCP
Track GLS Group Europe parcels (gls-group.eu parcel tracking) via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.
Packeta (Zásilkovna) Tracking API & MCP
Track Packeta (Zásilkovna) parcels (Z-numbers, Czech, Slovak, Polish, Hungarian and Romanian pickup points) via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.