Carriers

Kuehne+Nagel Tracking API & MCP

Query live Kuehne+Nagel (kuehnenagel) package status and scan history in a single synchronous GET request or MCP tool call.

Overview & Quick Facts

PropertyValue
Carrier slug (?carrier=)kuehnenagel
Brand aliasesKuehne+Nagel, Kuehne Nagel, Kühne + Nagel, KN, mykn.kuehne-nagel.com
CategoryFreight forwarding and road logistics
Single-package REST endpointGET https://api.lastscanned.com/v1/track/{trackingNumber}
Batch REST endpointGET https://api.lastscanned.com/v1/track?numbers=RWM009228162,...
MCP server (https://mcp.lastscanned.com)track_package, track_packages, list_carriers
Authentication & pricingAuthorization: Bearer lsk_live_... · 1 free keyless lookup/day per IP

Tracking Number Formats & Auto-Detection

PassRule / RegexCheck DigitExamples
Pass 1 (matches)nonenonenone
Pass 2 (mayMatch)/^RWM\d{9}$/ or /^\d{2}A\d{9}$/noneRWM009228162

RWM numbers are also claimed by an earlier carrier in detection, so pass ?carrier=kuehnenagel for Kuehne+Nagel references.

Synchronous GET Request & Normalized JSON Response

curl -s "https://api.lastscanned.com/v1/track/RWM009228162?carrier=kuehnenagel" \
  -H "Authorization: Bearer $LASTSCANNED_API_KEY"
{
  "carrier": "kuehnenagel",
  "trackingNumber": "RWM009228162",
  "status": "delivered",
  "statusDescription": "Proof of delivery available",
  "service": "road",
  "deliveredAt": "2026-06-04T09:04:00Z",
  "deliveredAtLocal": "2026-06-04T09:04:00",
  "signedBy": null,
  "destination": {
    "city": "OLESNICA SLASKA",
    "state": null,
    "country": "PL"
  },
  "events": [
    {
      "timestamp": "2026-06-04T09:04:00Z",
      "localTime": "2026-06-04T09:04:00",
      "status": "delivered",
      "description": "Proof of delivery available",
      "location": null,
      "code": "pod-available"
    },
    {
      "timestamp": "2026-06-04T08:04:00Z",
      "localTime": "2026-06-04T10:04:00",
      "status": "delivered",
      "description": "Cargo delivered",
      "location": "OLESNICA SLASKA, PL",
      "code": "cargo-delivered"
    },
    {
      "timestamp": "2026-06-04T05:21:00Z",
      "localTime": "2026-06-04T07:21:00",
      "status": "out_for_delivery",
      "description": "In delivery",
      "location": "Wroclaw, PL",
      "code": "in-delivery"
    },
    {
      "timestamp": "2026-05-29T07:12:00Z",
      "localTime": "2026-05-29T09:12:00",
      "status": "in_transit",
      "description": "Vehicle arrived",
      "location": "Poznan, PL",
      "code": "vehicle-arrived"
    },
    {
      "timestamp": "2026-05-26T10:00:00Z",
      "localTime": "2026-05-26T10:00:00",
      "status": "label_created",
      "description": "Booking submission",
      "location": null,
      "code": "booking-submission"
    }
  ]
}

Notes

  • Three calls: the shipment list finds the shipment, then its route (location milestones) and information milestones are read. Only milestones that have happened are shown; planned ones are left out.
  • Times: every milestone has its own UTC offset, so timestamp and localTime are both exact.
  • Detection: the RWM shape is claimed by another carrier first, so Kuehne+Nagel is only reached with ?carrier=kuehnenagel.

4-72 Tracking API & MCP

Track 4-72 (Colombia) parcels via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.

MailPlus Tracking API & MCP

Track MailPlus parcels 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 ResponseNotesRelated Resources