Chronopost Tracking API & MCP

Query live Chronopost (chronopost) parcel status and scan history in a single synchronous GET request or MCP tool call. lastscanned reads Chronopost's own tracking web service and returns a normalized TrackingResult JSON payload, with every scan's UTC time worked out from the offset Chronopost prints. Chronopost S10 numbers ending FR also auto-detect to La Poste; pass ?carrier=chronopost to read Chronopost's own record.

Overview & Quick FactsCopy Anchor Link

Why developers use lastscanned for ChronopostCopy Anchor Link

• No tracking-page bot wall: chronopost.fr serves its tracking page behind a Cloudflare challenge. lastscanned calls the web service the page itself relies on, so a single fetch() returns JSON-shaped results instead.
• Exact UTC times: Chronopost prints each scan with its offset (+02:00 in summer, +01:00 in winter). lastscanned keeps that offset, so timestamp is correct in both seasons.
• Scan codes kept: events[].code holds Chronopost's own code (D delivered, TA in delivery, BL premises closed, SK waiting for information, PE collected by the carrier).

Tracking Number Formats & Auto-Detection (matches vs ?carrier=chronopost)Copy Anchor Link

When is ?carrier=chronopost required?Copy Anchor Link

• Always for Chronopost-only lookups: no number shape belongs to Chronopost alone. UPU S10 numbers ending FR (check digit valid) route to La Poste in Pass 1, which also answers for Chronopost parcels. Add ?carrier=chronopost to ask Chronopost's own service instead.

Synchronous GET Request & Normalized JSON ResponseCopy Anchor Link

curlCopy Anchor Link

curl -s "https://api.lastscanned.com/v1/track/XX123456789FR?carrier=chronopost" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"

JavaScript / TypeScript (fetch)Copy Anchor Link

const res = await fetch("https://api.lastscanned.com/v1/track/XX123456789FR?carrier=chronopost", {
  headers: { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` },
});
const pkg = await res.json();
console.log(pkg.status, pkg.events[0]);

MCP track_package tool callCopy Anchor Link

{
  "tool": "track_package",
  "arguments": {
    "tracking_number": "XX123456789FR",
    "carrier": "chronopost"
  }
}

Normalized TrackingResult JSON responseCopy Anchor Link

{
  "carrier": "chronopost",
  "trackingNumber": "XX123456789FR",
  "status": "out_for_delivery",
  "statusDescription": "Shipment in delivery to the consignee",
  "service": null,
  "deliveredAt": null,
  "deliveredAtLocal": null,
  "signedBy": null,
  "destination": null,
  "events": [
    {
      "timestamp": "2026-10-26T09:15:37Z",
      "localTime": "2026-10-26T10:15:37",
      "status": "out_for_delivery",
      "description": "Shipment in delivery to the consignee",
      "location": "TOURS CHRONOPOST 37000",
      "code": "TA"
    },
    {
      "timestamp": "2026-10-25T17:02:11Z",
      "localTime": "2026-10-25T18:02:11",
      "status": "in_transit",
      "description": "Sorted at delivery location",
      "location": "TOURS CHRONOPOST 37000",
      "code": "SD"
    },
    {
      "timestamp": "2026-10-24T14:40:03Z",
      "localTime": "2026-10-24T16:40:03",
      "status": "in_transit",
      "description": "Parcel collected by Carrier",
      "location": "AVIGNON CHRONOPOST 84000",
      "code": "PE"
    }
  ]
}

No record: a number Chronopost has no scans for returns not_found. Scan locations are the Chronopost agency name and its postcode; Chronopost's service gives no package-level status, so status comes from the newest scan.

Related ResourcesCopy Anchor Link

• Live browser lookup tool: Track a Chronopost package live on lastscanned.com/lookup/chronopost
• Carrier hub: All supported carriers
• Regex & check digits: Tracking number formats & auto-detection
• AI support workflows: WISMO AI agents & synchronous tracking