Carriers

La Poste / Colissimo / Chronopost Tracking API & MCP

Query live La Poste (laposte, covering Colissimo, Chronopost and tracked mail such as Lettre suivie and Recommandé) package status and scan history in a single synchronous GET request or MCP tool call. lastscanned auto-detects Colissimo parcel numbers and UPU S10 numbers ending FR.

Overview & Quick Facts

PropertyValue
Carrier slug (?carrier=)laposte
Brand & service aliasesLa Poste, Colissimo, Chronopost, Lettre suivie, Recommandé
Single-package REST endpointGET https://api.lastscanned.com/v1/track/{trackingNumber}
Batch REST endpointGET https://api.lastscanned.com/v1/track?numbers=NUMBER1,NUMBER2
MCP server (https://mcp.lastscanned.com)track_package, track_packages, list_carriers (claude mcp add --transport http lastscanned https://mcp.lastscanned.com)
Authentication & pricingAuthorization: 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

PassRuleCheck DigitExamples
Pass 1 (matches) — Colissimo1 digit, 1 letter, then 11 digits (13 characters)GS1 mod-10 over the 11 digits6A12345678905
Pass 1 (matches) — UPU S102 letters, 9 digits, FRUPU S10 mod-11RR123456785FR
Pass 2 (mayMatch)None——

Chronopost numbers that are not S10 shaped need ?carrier=laposte.

Synchronous GET Request & Normalized JSON Response

curl

curl -s "https://api.lastscanned.com/v1/track/6A12345678905" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"

JavaScript / TypeScript (fetch)

const res = await fetch("https://api.lastscanned.com/v1/track/6A12345678905", {
  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": "6A12345678905"
  }
}

Normalized TrackingResult JSON response

{
  "carrier": "laposte",
  "trackingNumber": "6A12345678905",
  "status": "in_transit",
  "statusDescription": "Votre Colissimo est en cours de traitement sur le site de tri local.",
  "service": "Colissimo",
  "deliveredAt": null,
  "deliveredAtLocal": null,
  "signedBy": null,
  "destination": null,
  "estimatedDelivery": null,
  "message": null,
  "events": [
    {
      "timestamp": "2026-10-08T06:59:01Z",
      "localTime": "2026-10-08T08:59:01",
      "status": "in_transit",
      "description": "Votre Colissimo est en cours de traitement sur le site de tri local.",
      "location": "FR",
      "code": "EP1"
    }
  ]
}

Notes

  • Scan wording is French, as La Poste prints it. Each scan carries its own UTC offset, so timestamp is exact.
  • A number La Poste has no scans for yet, and a number with a wrong check digit, both come back as not_found.
  • When the parcel goes on under a partner's number (international Colissimo), message reads "Handed to <partner> as <number>".

TopYou Tracking API & MCP

Track TopYou (Topyou Express cross-border parcels) via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.

PostNL Tracking API & MCP

Track PostNL parcels (3S barcodes and S10 numbers ending NL) via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.

On this page

Overview & Quick FactsTracking Number Formats & Auto-DetectionSynchronous GET Request & Normalized JSON ResponsecurlJavaScript / TypeScript (fetch)MCP track_package tool callNormalized TrackingResult JSON responseNotesRelated Resources