Carriers
Veloces Tracking API & MCP
Query live Veloces (veloces) package status and scan history in a single synchronous GET request or MCP tool call. Pass ?carrier=veloces (or the MCP carrier argument) so the lookup goes to Veloces.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | veloces |
| Brand aliases | Veloces, Veloces Delivery, veloces.app |
| Category | Regional (last-mile courier, Colombia / Mexico / Ecuador / Chile) |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber} |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=V4000919466,... |
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) | /^V\d{10}$/ | none | V4000919466 |
V plus ten digits is tried only when no other carrier claims the number; pass ?carrier=veloces to be sure.
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/V4000919466?carrier=veloces" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"{
"carrier": "veloces",
"trackingNumber": "V4000919466",
"status": "delivered",
"statusDescription": "Entregado",
"service": null,
"deliveredAt": "2026-03-12T20:32:39Z",
"deliveredAtLocal": "2026-03-12T20:32:39",
"signedBy": null,
"destination": {
"city": "QUITO",
"state": null,
"country": null
},
"events": [
{
"timestamp": "2026-03-12T20:32:39Z",
"localTime": "2026-03-12T20:32:39",
"status": "delivered",
"description": "Entregado",
"location": null,
"code": "4"
},
{
"timestamp": "2026-03-12T14:49:40Z",
"localTime": "2026-03-12T14:49:40",
"status": "out_for_delivery",
"description": "En Camino",
"location": null,
"code": "8"
},
{
"timestamp": "2026-03-11T00:18:52Z",
"localTime": "2026-03-11T00:18:52",
"status": "exception",
"description": "Novedad: No contesta",
"location": null,
"code": "5"
},
{
"timestamp": "2026-03-08T15:02:18Z",
"localTime": "2026-03-08T15:02:18",
"status": "label_created",
"description": "Guía Generada",
"location": null,
"code": "1"
}
]
}Notes
- Statuses:
codeis Veloces' status id (1 guide generated, 11 picked up, 2 and 13 warehouses, 3 on route, 8 on the way to the recipient, 5 and 17 incident, 4 delivered). An incident's note (for exampleNo contesta) is appended. - Time zone: Veloces runs in several countries and the API gives UTC only, so
localTimeis the UTC clock time.
Related Resources
- Regex & check digits: Tracking number formats & auto-detection
Uzbekistan Post Tracking API & MCP
Track Uzbekistan Post (UzPost, S10 numbers ending UZ) parcels and their scan history via synchronous REST GET or MCP. Normalized JSON status and events, no carrier credentials required.
Via Cargo Tracking API & MCP
Track Via Cargo (Argentina) parcels and their scan history via synchronous REST GET or MCP. Normalized JSON status and events, no carrier credentials required.