For Agents
Look up real-time shipment status and milestone events for any DHL parcel or freight shipment across all divisions through one tracking endpoint.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DHL Unified Shipment Tracking 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with DHL Unified Shipment Tracking API API.
Look up shipment status by tracking number across all DHL divisions
Retrieve milestone events with timestamps for a shipment journey
Identify which DHL division is responsible for a given shipment
Filter tracking responses by service, origin, and destination country
GET STARTED
Use for: I need to track a DHL shipment by tracking number, Check whether a parcel has been delivered, Retrieve the full event history for a shipment, Find the current location of an in-transit shipment
Not supported: Does not handle label creation, rate quotes, or pickup booking — use for DHL shipment tracking lookups only.
The DHL Unified Shipment Tracking API returns real-time status updates for shipments across DHL Express, eCommerce, Freight, and Supply Chain through a single GET /shipments endpoint. Given a tracking number, it returns the current shipment state, milestone history, and the responsible DHL division. It is the canonical way to integrate cross-divisional DHL tracking from a storefront, customer-service tool, or operations dashboard.
Detect when a shipment reaches the out-for-delivery or delivered state
Surface estimated delivery dates where DHL has computed them
Patterns agents use DHL Unified Shipment Tracking API API for, with concrete tasks.
★ Order Tracking on Customer Storefront
Display a real-time tracking timeline on an order details page without picking the right DHL divisional API for each shipment. One call to GET /shipments returns status, events, and estimated delivery, making it suitable for both Express and standard parcel shipments. This simplifies the storefront integration to a single tracking client.
Given tracking number JJD1234567890, render the milestone timeline and the estimated delivery date on the order details page
Operations Exception Monitoring
Run a daily reconciliation job that flags shipments stuck in transit, returned to sender, or otherwise off the expected path. The tracking endpoint returns the latest milestone for each tracking number, which an operations dashboard can compare against expected delivery windows. This makes it possible to surface exceptions before customers complain.
For every tracking number in yesterday's outbound batch, fetch the current status and flag any whose latest event is older than 48 hours and not yet delivered
Customer Notification Automation
Send the customer an SMS or email the moment their parcel changes state. By polling the tracking endpoint and comparing the latest milestone against the previous one, an automation can trigger out-for-delivery and delivered notifications even when the carrier does not push webhooks back. Useful for retailers without a dedicated tracking partner.
Poll tracking number 1234567890 every hour and send a templated SMS the first time the latest event status equals out-for-delivery or delivered
AI Agent Where-Is-My-Order Bot
An AI customer-service assistant can answer shipping queries by calling the DHL unified tracking endpoint through Jentic. The agent searches by intent ("track a shipment"), loads the input schema, executes with the user's tracking number, and summarises the milestone history in natural language without needing the OpenAPI spec.
When the user provides a tracking number, call the DHL tracking endpoint, summarise the current status and ETA, and offer to keep watching the shipment until it is delivered
1 endpoints — the dhl unified shipment tracking api returns real-time status updates for shipments across dhl express, ecommerce, freight, and supply chain through a single get /shipments endpoint.
METHOD
PATH
DESCRIPTION
/shipments
Retrieve tracking status and event history for a shipment
/shipments
Retrieve tracking status and event history for a shipment
Three things that make agents converge on Jentic-routed access.
Credential isolation
DHL API keys live in the Jentic vault. Agents receive scoped execution access — the raw key never enters the model's prompt context.
Intent-based discovery
Agents express intent in natural language ("track a shipment") and Jentic returns the matching DHL operation with its input schema.
Time to first call
Direct DHL integration: half a day for auth and response parsing. Through Jentic: under 30 minutes.
Alternatives and complements available in the Jentic catalogue.
DHL Shipment Tracking - Unified API
Identical surface area under a slightly different naming — the canonical "Unified API" entry
Prefer the Shipment Tracking - Unified API entry; this slug exists for backward compatibility
DHL eCommerce (Netherlands) API
Label creation and shipment options for DHL Parcel in the Netherlands
Use when the agent needs to create labels alongside tracking in the Dutch DHL Parcel network
Specific to using DHL Unified Shipment Tracking API API through Jentic.
What authentication does the DHL Unified Shipment Tracking API use?
The API uses an API key passed in a request header. Keys are issued from the DHL Developer Portal. Through Jentic the key is stored in the encrypted vault and injected only at execution time.
Can a single call track shipments from any DHL division?
Yes. GET /shipments accepts a tracking number across Express, eCommerce, Freight, and Supply Chain. The response identifies which division handled the shipment and returns a unified status and milestone timeline.
What are the rate limits for the DHL Unified Shipment Tracking API?
Rate limits are tier-based and set when the API key is provisioned. Free tier keys are typically capped at 250 requests per day; higher tiers expand that allowance. Check the DHL Developer Portal for the limit attached to your key.
How do I track a parcel through Jentic?
Run a Jentic search for "track a DHL shipment". Jentic returns the tracking operation with its input schema (trackingNumber as a query parameter), the agent loads the schema, and executes. Optional filters include service and originCountryCode.
Does the response include estimated delivery dates?
Yes, when DHL has computed one. The shipment response includes an estimatedTimeOfDelivery field for divisions that publish ETAs and a list of milestone events with timestamps.
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. Sign up at https://app.jentic.com/sign-up.