Cirro E-Commerce Tracking API & MCP

Query live Cirro E-Commerce (cirro) package status and scan history in a single synchronous GET request or MCP tool call. lastscanned auto-detects 14-character CR… and 17-character CIFR… tracking numbers and returns a normalized TrackingResult JSON payload—without requiring Cirro shipper credentials, HMAC-SHA256 request signing, or webhook infrastructure.

Overview & Quick FactsCopy Anchor Link

Why developers use lastscanned for Cirro E-CommerceCopy Anchor Link

• Skip Nebula HMAC-SHA256 signing & rate-limit CAPTCHAs: Direct calls to Cirro's tracking endpoint require computing an HMAC-SHA256 Nebula token: signature over Timestamp + NumberList and trigger CAPTCHA error codes (1003 / 1004) when polled repeatedly from a single backend IP. Calling GET https://api.lastscanned.com/v1/track/:number works cleanly in one fetch().
• Unified Cirro + GOFO network coverage: Following GOFO Express's 2026 acquisition of Cirro E-Commerce, CR… and CIFR… parcels move seamlessly through GOFO's US last-mile hubs while preserving full origin-to-doorstep scan visibility.

Tracking Number Formats & Auto-Detection (matches vs mayMatch)Copy Anchor Link

Cirro is evaluated fourteenth (#14) in lastscanned's two-pass detector:

Disambiguating Cirro vs GOFO (?carrier=cirro)Copy Anchor Link

• Auto-detected (CR + 12 digits and CIFR + 13 digits): No ?carrier= parameter is needed.
• When ?carrier=cirro is required: Shipper order numbers starting with SKP… (SKP919023354) or GFUS… numbers that you specifically want to inspect via Cirro's endpoint instead of gofo.

Synchronous GET Request & Normalized JSON ResponseCopy Anchor Link

curlCopy Anchor Link

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

JavaScript / TypeScript (fetch)Copy Anchor Link

const res = await fetch("https://api.lastscanned.com/v1/track/CR010740141269", {
  headers: { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` },
});
const pkg = await res.json();
console.log(pkg.status, pkg.statusDescription, pkg.deliveredAt);

MCP track_package tool callCopy Anchor Link

{
  "tool": "track_package",
  "arguments": {
    "tracking_number": "CR010740141269"
  }
}

Normalized TrackingResult JSON responseCopy Anchor Link

{
  "carrier": "cirro",
  "trackingNumber": "CR010740141269",
  "status": "delivered",
  "statusDescription": "Your package has been delivered, Left at Front Door",
  "service": null,
  "deliveredAt": "2026-10-25T19:08:44Z",
  "deliveredAtLocal": "2026-10-25T15:08:44",
  "signedBy": "J. DOE",
  "destination": {
    "city": "PHILADELPHIA",
    "state": "PA",
    "country": "US"
  },
  "estimatedDelivery": null,
  "events": [
    {
      "timestamp": "2026-10-25T19:08:44Z",
      "localTime": "2026-10-25T15:08:44",
      "status": "delivered",
      "description": "Your package has been delivered, Left at Front Door",
      "location": "PHILADELPHIA, PA",
      "code": "Delivered"
    },
    {
      "timestamp": null,
      "localTime": "2026-10-25T08:19:10",
      "status": "out_for_delivery",
      "description": "Your package is out for delivery",
      "location": "PHILADELPHIA, PA",
      "code": "Transit"
    },
    {
      "timestamp": null,
      "localTime": "2026-10-24T22:41:05",
      "status": "in_transit",
      "description": "Arrived at Sorting Center",
      "location": "CARLSTADT, NJ",
      "code": "Transit"
    },
    {
      "timestamp": null,
      "localTime": "2026-10-22T10:15:00",
      "status": "label_created",
      "description": "Shipment information received",
      "location": null,
      "code": "Processing"
    }
  ]
}

Raw status & scan codes: events[].code preserves Cirro's StatusCode ("Processing", "Transit", "Delivered", "Alert", "FailedAttempt", "Exception", "Return", "Returned"), while lastscanned also inspects the event description to promote "out for delivery" scans inside the "Transit" category to out_for_delivery.

Carrier-Specific Status & Integration NotesCopy Anchor Link

• Latest scan UTC (timestamp) vs historical localTime: Cirro provides an explicit GMT±HH:MM timezone (GmtProcessTimezone) only on the latest scan (LastTrackEvent), while historical rows in DetailList report local wall-clock time (ProcessTime) without a per-row offset. Therefore, events[0].timestamp (and deliveredAt) is populated in UTC, while earlier scans populate localTime with timestamp: null.
• Up to 20 numbers per upstream batch: lastscanned automatically chunks larger Cirro batches so you can pass up to 35 Cirro numbers in a single GET /v1/track?numbers=... request.

Related ResourcesCopy Anchor Link

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