Search

Use our API to retrieve a list of the most recently created trackings.

Details of how the v2/search endpoint can be used to retrieve a list of the most recently created trackings in the parcelLab system are described below.

Search recent trackings

get

Retrieves recent trackings from the parcelLab system. The response gives some meta information and then a list of all recently created trackings, sorted descending via the timestamp of creation (can be found in results[].cre.dat)

Authorizations

Authorization

AuthorizationstringRequired

Use the format Parcellab-API-Token <your-base64-encoded-api-key>

Header parameters

Content-Typestring · enumRequired

Must be application/json

Possible values:

Body

application/json

sstringOptional

Any search term or reference number

Example: 66d8980c0c49874aecd20b68

pintegerOptional

What page to show (pagination). Defaults to 0.

Example: 0

pSizeintegerOptional

Number of entries on a page. Defaults to 24.

Example: 15

fromstringOptional

The date range to filter by in YYYY-MM-DD format. Defaults to last 7 days.

Example: 2025-05-07

countrystringOptional

Comma-separated list of destination_country_iso3 codes in ISO 3166-1 alpha-3 or alpha-2 format to filter by.

Example: DEU

courierstringOptional

Comma-separated list of courier codes to filter by.

Example: dhl-germany

clientstringOptional

Comma-separated list of client codes as provided on tracking.

Example: 1612197

returnbooleanOptional

If true, only return trackings are shown. If false, only outbound trackings are shown. If empty, then both are shown.

Example: false

branchDeliverybooleanOptional

If true, only branch deliveries are shown. If empty, then all are shown.

Example: true

Responses

200

Request successful

application/json

401

Unauthorized request

application/json

500

Internal server error

application/json

get

/v2/search

HTTPcURLJavaScriptPython

GET /v2/search HTTP/1.1
Host: api.parcellab.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 33

{
  "client": 1612197,
  "return": false
}

Retrieve recent outbound trackingsMonitor the success of data transmission

{
  "meta": {
    "hits": 1612,
    "searchTime": 44,
    "assemblyTime": 6
  },
  "results": [
    {
      "id": "xxx",
      "tn": "xxx",
      "co": {
        "n": "dhl-germany",
        "p": "DHL"
      },
      "inf": {},
      "oth": {},
      "cre": {
        "dat": "2019-01-01T16:12:00.000Z",
        "ago": "16 minutes ago"
      },
      "lst": {},
      "rep": {}
    }
  ]
}

Checking Last Transfer via API

If you want to programmatically monitor the success of any data transmission, you can do so by calling the latest submitted records and checking the timestamp. For all details of this request, see the information below, which shows a useful API call to check the most recent data transmission.

curl -L \
  --url 'https://api.parcellab.com/v2/search' \
  --header 'Authorization: Parcellab-API-Token <your-API-token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "pSize": 1
  }'

This returns exactly on result, hence the timestamp of the most recent successful data transmission can be found at response.results[0].cre.dat and has the format YYYY-MM-DDTHH:mm:ss.sssZ.