Skip to content
Navo24 Navo24
GETAPI key

Detect the carrier

GETparcel.navo24.com/v1/parcel/detect

Which connected sources a number can belong to, best first, with the UPU S10 check digit result. No source is called.

Query parameters

numberstringrequired

Tracking number.

Response schema

6 fields

Derived from the example response, nested as the JSON is.

dataobject

The payload. Everything an endpoint returns sits under this key.

numberstring
candidatesobject[]
candidates[]object
idstring

Stable identifier for the record. On the tracking endpoints this is the container UUID, except on a portfolio summary row, where it is the container number.

namestring

Human-readable name.

s10_validboolean

Errors

A failure carries { "ok": false, "error": { "code", "message", "severity" } }. Branch on the code, and log the message.

missing_key401

No key in Authorization or x-api-key.

invalid_key401

The key is unknown or revoked.

rate_limited429

More than 40 requests in one minute from one client.

upstream_error502

A source did not answer. Retry in a minute.

curl 'https://parcel.navo24.com/v1/parcel/detect?number=RB123456785CN' \
  -H "Authorization: Bearer tmcp_YOUR_API_KEY"
Response
{
  "data": {
    "number": "RB123456785CN",
    "candidates": [
      {
        "id": "cainiao",
        "name": "Cainiao (AliExpress, China Post)"
      },
      {
        "id": "ems",
        "name": "EMS (UPU network)"
      }
    ],
    "s10_valid": true
  }
}