DHL Shipment Tracking

Track DHL Express, eCommerce, Parcel, Freight and Same Day shipments through DHL's Unified Shipment Tracking API.

Bring DHL status, ETAs and scan events into order, service and customer notification flows across every DHL business.

Build a flow with DHL Shipment Tracking Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

shipment events

List tracking events
Source
Every scan event for a tracking number, one record per event.
shipment_events.list

shipments

Track shipment
Source
Shipments matching a tracking number, with status, ETA, origin, destination and details.
shipments.list

Authentication

DHL API Developer Portal consumer key

Plans and access

Free DHL API Developer Portal app subscribed to Shipment Tracking - Unified. Default quota is 250 calls per day and at most one call every 5 seconds; request a higher quota in the portal.

Test environment

api-sandbox.dhl.com returns mocked responses for any subscribed key; DHL's documented example number 7777777770 works there.

Rate limits

Default 250 calls per day and one call every 5 seconds per app; HTTP 429 when exceeded.

Pagination

offset and limit with nextUrl; Nexra follows nextUrl.

Provider events

DHL offers push tracking only through separate business-specific products. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Tracking only: DHL has no read-only list of an account's shipments in this API, and one tracking number is queried per request.
DHL Express MyDHL API (rating, shipment creation, pickups) uses a different host (express.api.dhl.com) and HTTP Basic credentials, so it is not part of this connector.
DHL Location Finder runs on api.dhl.com, a different origin from tracking, so service point search is not included.
The health check tracks DHL's documented example number 7777777770. It succeeds on the sandbox; in production DHL may answer 404 for that number, which reports the connection as not found even though the key is valid.
Detail depends on the DHL business: recipientPostalCode unlocks full data for parcel-de and parcel-nl.

Developer reference

Create the DHL Group credentials described above with the narrowest permissions your flows need.
In Nexra, open Connect, then Connections, then New connection, choose DHL Shipment Tracking, enter its settings and credentials, and tick only the write actions you need. Connection guide
Test the connection, then use its actions as flow sources and destinations. Flow guide

DHL Group docsAPI reference DHL Group docsAuthentication DHL Group docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/dhl and the Connections API.