DHL Shipment Tracking - Unified API
Browse all Dhl APIs74
AI ReadinessAI-Aware (A-)74/100
Official vendor OpenAPI document · agent-readyE CommerceShipping LogisticsapiKey1 EndpointsREST
For Agents
Look 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.
Use for: I need to track a DHL shipment by tracking number, Check whether a parcel was delivered, Retrieve the milestone history for a shipment, Find the estimated delivery date for an order
Not supported: Does not handle label creation, rate quotes, or pickup scheduling - use for DHL shipment tracking lookups only.
The DHL Unified Shipment Tracking API consolidates real-time tracking across every DHL division - Express, Parcel, eCommerce, Freight, and Supply Chain - behind a single GET /shipments endpoint. Given a tracking number, it returns current status, milestone events, the responsible service provider, origin and destination addresses, and estimated delivery dates. It is the canonical way to integrate DHL tracking without picking the right divisional API for each shipment.
Install Jentic One Beta
Connect the DHL Shipment Tracking - Unified API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DHL Shipment Tracking - Unified API, 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%2Fdhl-shipment-tracking-unified-api" | 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%2Fdhl-shipment-tracking-unified-api" | 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.
Capabilities
What an agent can do with DHL Shipment Tracking - Unified API.
Look up shipment status by tracking number across all DHL service divisions
Retrieve detailed milestone events and timestamps for a shipment journey
Identify which DHL division or service provider is handling a given shipment
Verify origin and destination address details captured at pickup
Filter tracking results by language, service, origin country, and destination country
Detect delivery completion and proof-of-delivery information
Use Cases
Patterns agents use DHL Shipment Tracking - Unified API for, with concrete tasks.
★ Customer Order Tracking Page
Power a branded order-tracking page on an e-commerce storefront without integrating each DHL division separately. A single call to GET /shipments returns the current status, a milestone timeline, and the estimated delivery date, regardless of whether the underlying carrier is DHL Express, Parcel, or Freight. This collapses what used to be multiple integrations into one.
Fetch tracking events for tracking number 1234567890, render the timeline on the order page, and show the estimated delivery date
Proactive Delivery Notifications
Trigger SMS or email notifications when a DHL shipment hits a particular milestone such as out-for-delivery or delivered. By polling the unified tracking endpoint and comparing the latest event against the previous state, an automation can fire alerts to customers without waiting for vendor-side webhooks. Useful for high-value shipments where customers expect proactive updates.
Poll tracking number 9876543210 every 30 minutes and send an SMS when the latest event status moves to delivered
Logistics Reporting and Reconciliation
Reconcile shipped orders against DHL records by pulling the final status of every tracking number in a daily batch. The unified endpoint accepts a tracking number plus filters for service, origin country, and destination country, making it straightforward to identify shipments that are stuck, returned, or mis-routed. Operations teams use this to flag exceptions for manual review.
For each tracking number in yesterday's order batch, fetch the latest shipment status and flag any whose status is not delivered or transit
AI Agent Customer-Service Assistant
A customer-service agent powered by an LLM can answer "Where is my package?" by calling the unified tracking endpoint through Jentic. The agent searches Jentic for "track a shipment", loads the input schema, and executes the call with the user's tracking number, then summarises the milestone history in natural language.
Given user tracking number 1234567890, call the DHL unified tracking endpoint, summarise the latest status and ETA, and offer to send updates when the status changes
Key Endpoints
1 endpoints — the dhl unified shipment tracking api consolidates real-time tracking across every dhl division - express, parcel, ecommerce, freight, and supply chain - behind a single get /shipments endpoint.
METHOD
PATH
DESCRIPTION
GET
/shipments
Retrieve tracking status and events for a shipment by tracking number
GET
/shipments
Retrieve tracking status and events for a shipment by tracking number
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
D
DHL Shipment Tracking - Unified API
- AI-Aware (A-)74/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility70
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
70
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: A-Signals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
100%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the DHL Shipment Tracking Unified API by hand means setting the DHL-API-Key header against the EU tracking host and handling the query parameters for the shipments lookup yourself. Through Jentic you install once, import the DHL Shipment Tracking Unified API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The API exposes a single read-only shipments lookup, so the agent can only track shipments and nothing else, and you decide whether to give it that one operation. 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 at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'track a shipment', and Jentic returns the DHL tracking operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DHL Shipment Tracking - Unified API through Jentic.
What authentication does the DHL Shipment Tracking - Unified API use?
The API uses an API key passed in the DHL-API-Key request header. Through Jentic the key is stored in the encrypted vault and injected at execution time, so it never enters the agent's prompt context.
Can I track shipments from any DHL division with one call?
Yes. GET /shipments accepts a tracking number across DHL Express, Parcel, eCommerce, Freight, and Supply Chain. The response identifies which service provider is handling the shipment and returns a unified status and event timeline.
What are the rate limits for the DHL Shipment Tracking - Unified API?
DHL applies tier-based rate limits set when the API key is provisioned in the DHL Developer Portal. Free tier keys are limited to 250 requests per day; commercial tiers raise that ceiling. Check the developer portal for your specific allocation.
How do I look up a tracking number through Jentic?
Run a Jentic search for "track a DHL shipment". Jentic returns the DHL unified tracking operation, you load the schema (it requires the trackingNumber query parameter), and execute. Optional filters include service, originCountryCode, and language.
Does the API return proof-of-delivery information?
Yes, when DHL has captured it. The shipment response includes a delivered event with a timestamp, recipient signature reference, and address details for divisions that record proof of delivery.
How do I install the Jentic SDK to call DHL tracking?
Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then use Jentic with SearchRequest, LoadRequest, and ExecutionRequest. Get started with Jentic One, the self-hosted execution layer.
Can I limit what my agent is allowed to do with the DHL Shipment Tracking - Unified API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only a single read-only GET /shipments lookup. That means the agent can track shipments by tracking number and nothing more; it cannot create labels, quote rates, or schedule pickups. You also control whether the agent is granted that one operation and whether your stored DHL API key is injected at execution time.
GET STARTED