DHL APIs for AI Agents
E CommerceShipping LogisticsOfficial Vendor SpecsAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints2 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceOfficial OpenAPI specs
An agent can look up the real-time status, milestone timeline, responsible division, and estimated delivery date of any DHL shipment by tracking number, then monitor it until it reaches out-for-delivery or delivered and summarise the journey for a customer.
DHL's Jentic surface is built around one unified tracking endpoint that spans every DHL division, so an agent tracks Express, Parcel, eCommerce, Freight, and Supply Chain shipments through the same call rather than routing each shipment to a division-specific API.
DHL API Catalog
2 APIs across 1 product group. All share one credential.
E Commerce2
DHL Shipment Tracking - Unified APILook up real-time shipment status, milestone events, and estimated delivery dates for any DHL shipment across Express, Parcel, eCommerce, Freight, and Supply Chain through a single endpoint.~1 endpointDHL Unified Shipment Tracking APILook up real-time shipment status and milestone events for any DHL parcel or freight shipment across all divisions through one tracking endpoint.~1 endpoint
Which DHL API should I use?
| I want to... | Use |
|---|---|
| Track a DHL shipment across any division by tracking number | DHL Shipment Tracking - Unified API |
| Track a shipment via a legacy integration referencing the older name | DHL Unified Shipment Tracking API |
Install Jentic One Beta
Connect the DHL APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DHL APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdhl.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdhl.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “track a dhl shipment across any division”.
What AI Agents Can Do with DHL
Each workflow spans multiple DHL APIs. Jentic routes each operation to the right API automatically.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring DHL tracking by hand means setting the DHL API key header against the EU tracking host and handling the shipments query parameters yourself for each integration. With Jentic you install Jentic One once, add the DHL tracking API from the Jentic directory, store the key once, and your agent calls it.
Permission scoping
Both DHL APIs expose only a single read-only shipments lookup, so an agent can track shipments and nothing else. Your own Jentic One rules decide whether the agent gets that one operation, and it cannot create labels, quote rates, or schedule pickups.
Credential isolation
Your DHL API key is stored once, encrypted, by your own Jentic One instance and injected only at execution time. It never enters the agent's prompt, logs, or context, and the same key serves both tracking entries.
Intent-based discovery
An agent searches the Jentic directory by intent such as 'track a shipment' and gets back the matching DHL tracking operation with its input schema, so it calls the right endpoint without browsing the DHL reference docs.
FAQs
Specific to using DHL APIs through Jentic.
What can an agent do across DHL's APIs?
An agent can look up the real-time status of any DHL shipment by tracking number, retrieve its milestone history and timestamps, identify which DHL division is handling it, read origin and destination address details, and find the estimated delivery date. Every operation is a read-only tracking lookup.
Why are there two DHL tracking APIs and which should I use?
The two entries cover the same unified tracking surface under slightly different names. Prefer the DHL Shipment Tracking Unified API as the canonical entry; the DHL Unified Shipment Tracking API exists mainly for backward compatibility with earlier integrations that referenced the older name.
Can one call track shipments from any DHL division?
Yes. A single request to the shipments endpoint accepts a tracking number across DHL Express, Parcel, eCommerce, Freight, and Supply Chain. The response identifies which division or service provider handled the shipment and returns a unified status and milestone timeline.
Do these APIs let an agent create shipments or labels?
No. The DHL surface on Jentic is limited to tracking lookups. Creating labels, quoting rates, scheduling pickups, and managing returns are outside this portfolio and would require separate DHL shipping APIs.
Does one credential cover both APIs?
Yes. Both APIs authenticate with a single DHL API key passed in a request header and issued from the DHL Developer Portal. The same key works across both tracking entries, and DHL applies tier-based rate limits set when the key is provisioned.
Is proof of delivery and estimated delivery data available?
Yes, when DHL has captured or computed it. Responses can include a delivered event with a timestamp and recipient signature reference, plus an estimated delivery date for divisions that publish one, alongside the full list of milestone events.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.