Carriers
Vinted Go Tracking API & MCP
Query live Vinted Go (vintedgo) package status and scan history in a single synchronous GET request or MCP tool call.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | vintedgo |
| Brand aliases | VintedGo, Vinted Go Parcel, Vinted Go Locker |
| Category | Marketplace parcel-shop and locker delivery (FR, BE, NL, ES, PT) |
| Region | France / Benelux / Iberia |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber} |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=1780123456789012,... |
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) | /^1[78]\d{14}$/ | none | 1780123456789012 |
A 16-digit id beginning 17 or 18 that nothing else claims is tried against Vinted Go. Other carriers use 16 digits too, so pass ?carrier=vintedgo when in doubt.
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/1780123456789012?carrier=vintedgo" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"{
"carrier": "vintedgo",
"trackingNumber": "1780123456789012",
"status": "delivered",
"statusDescription": "Delivered",
"service": null,
"deliveredAt": "2026-09-07T11:47:06Z",
"deliveredAtLocal": "2026-09-07T11:47:06",
"signedBy": null,
"destination": null,
"events": [
{
"timestamp": "2026-09-07T11:47:06Z",
"localTime": "2026-09-07T11:47:06",
"status": "delivered",
"description": "Delivered",
"location": null,
"code": "delivered"
},
{
"timestamp": "2026-09-06T11:36:42Z",
"localTime": "2026-09-06T11:36:42",
"status": "exception",
"description": "Ready to collect at the parcel shop",
"location": "Example Street 1, Lisbon, PT",
"code": "ready_for_pickup"
},
{
"timestamp": "2026-09-05T06:19:18Z",
"localTime": "2026-09-05T06:19:18",
"status": "in_transit",
"description": "At sorting center in Lisbon, PT",
"location": "Lisbon, PT",
"code": "in_transit"
},
{
"timestamp": "2026-08-27T22:09:48Z",
"localTime": "2026-08-27T22:09:48",
"status": "label_created",
"description": "Shipment created",
"location": null,
"code": "created"
}
]
}Notes
- Time zone: events are UTC (
…Z). - Ready to collect: a parcel waiting at a shop or locker is reported as
exception, as the other carriers' ready for collection scans are.
Related Resources
- Regex & check digits: Tracking number formats & auto-detection
Venipak Tracking API & MCP
Track Venipak (Lithuania, Latvia, Estonia) parcels and shipment numbers via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.
Vozovoz Tracking API & MCP
Track Vozovoz parcels via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.