Carriers
99minutos Tracking API & MCP
Query live 99minutos (minutos99) package status and scan history in a single synchronous GET request or MCP tool call. 99minutos numbers are not auto-detected: the carrier's tracking IDs have no verified format, so pass ?carrier=minutos99.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | minutos99 |
| Brand & service aliases | 99minutos, 99 minutos (99minutos.com) |
| Category | Latin American last-mile courier (Mexico, Colombia, Chile) |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber}?carrier=minutos99 |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=99MX123456789,...&carrier=minutos99 |
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) |
Why developers use lastscanned for 99minutos
- Same status changes as the 99minutos tracking page: created, collected, in transit, out for delivery, delivered, with the comment the courier left.
- UTC timestamps: 99minutos sends each change as a UTC instant, so
timestampis set (the local time is not known).
Tracking Number Formats & Auto-Detection
| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
Pass 1 (matches) | None | — | — |
Pass 2 (mayMatch) | None | — | — |
Explicit (?carrier=minutos99) | The order's tracking ID from 99minutos | — | 99MX123456789 |
Synchronous GET Request & Normalized JSON Response
curl
curl -s "https://api.lastscanned.com/v1/track/99MX123456789?carrier=minutos99" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"JavaScript / TypeScript (fetch)
const res = await fetch("https://api.lastscanned.com/v1/track/99MX123456789?carrier=minutos99", {
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": "99MX123456789",
"carrier": "minutos99"
}
}Normalized TrackingResult JSON response
{
"carrier": "minutos99",
"trackingNumber": "99MX123456789",
"status": "out_for_delivery",
"statusDescription": "Pedido en camino hacia el domicilio",
"service": null,
"deliveredAt": null,
"deliveredAtLocal": null,
"signedBy": null,
"destination": null,
"events": [
{
"timestamp": "2026-10-25T16:20:00Z",
"localTime": "2026-10-25T16:20:00",
"status": "out_for_delivery",
"description": "Pedido en camino hacia el domicilio",
"location": null,
"code": "ToDelivery"
},
{
"timestamp": "2026-10-24T13:05:00Z",
"localTime": "2026-10-24T13:05:00",
"status": "in_transit",
"description": "Pedido en el almacén, en preparación para la entrega",
"location": null,
"code": "Warehouse"
},
{
"timestamp": "2026-10-23T10:45:00Z",
"localTime": "2026-10-23T10:45:00",
"status": "in_transit",
"description": "Pedido recogido en el negocio",
"location": null,
"code": "Collected"
}
]
}Notes
- Recipient verification: some orders make the 99minutos page ask the recipient to confirm their identity. Those return a lookup error here.
- Written from the page's own scripts: the not-found answer was checked live; the field names of a found order come from the page's code.
Related Resources
- Live browser lookup tool: Track a 99minutos package live on lastscanned.com/lookup/minutos99
- Carrier hub: All supported carriers
- Regex & check digits: Tracking number formats & auto-detection
- AI support workflows: WISMO AI agents & synchronous tracking
PostNet South Africa Tracking API & MCP
Track PostNet parcels with one synchronous REST GET or MCP call. Normalized JSON status and scan history, with no carrier credentials required.
Mainfreight Tracking API & MCP
Track Mainfreight parcels with one synchronous REST GET or MCP call. Normalized JSON status and scan history, with no carrier credentials required.