Parcel tracking for your own systems

Quickstart

Make your first tracking request

Send your API key in the Authorization header and the Global Express Local number in the JSON body.

curl --request POST \
  https://www.globalexpresslocal.com/api/v1/tracking \
  --header "Authorization: Bearer gel_live_your_api_key" \
  --header "Content-Type: application/json" \
  --data '{"tracking_number":"INDEMO8675309"}'

Authentication

Use a bearer API key

API keys belong in server-side configuration. Do not expose a live key in browser JavaScript, public repositories or support messages.

Endpoint

Returns the shipment summary and ordered timeline. The request does not require a postcode.

Request body

{
  "tracking_number": "INDEMO8675309"
}

Example successful response

All shipment details in this example are fictional.

{
  "data": {
    "tracking": "INDEMO8675309",
    "status": "In transit",
    "customerReference": "DEMO-482175",
    "sender": "Example Retail Group",
    "parcels": "3 parcels in total",
    "weight": "18kg",
    "events": [
      {
        "title": "dispatched",
        "detail": "Shipment created.",
        "time": "2026-08-28 09:15 UTC",
        "location": "China"
      }
    ]
  },
  "meta": {
    "requestId": "request-uuid",
    "eventCount": 1,
    "rateLimit": {
      "minute": 60,
      "daily": 1000
    }
  }
}

The events array contains the complete chronology in order, including shipments with five or more events.

Rate limits

Predictable limits for reliable service

Every response includes X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. A limited request returns HTTP 429 and a Retry-After header.

Errors

Standard HTTP responses