DHL is a global logistics company operating in over 220 countries and territories, and its developer surface on the APIs.io network reflects that scale. The provider carries an api_count of 48, spread across the company’s business divisions: DHL eCommerce, DHL Express, DHL Global Forwarding, DHL Freight, DHL Supply Chain, and Post and Parcel Germany. This is not one API. It is a control plane for moving parcels, pallets, and letters across a global network.
What’s in the surface
The catalog captures the full spread of DHL’s divisional APIs. A few anchor points:
- Location Finder Unified — a single interface to discover DHL locations across Post and Parcel Germany, DHL Express, DHL eCommerce, and DHL Freight. It is the OpenAPI-described spec (
dhl-openapi.yml) in the provider’sapi_specs. - Shipment Tracking Unified — status access across DHL Freight, eCommerce, Supply Chain, Global Forwarding, and Post and Parcel Germany through one tracking interface, plus a push-based variant that proactively sends updates.
- DHL Parcel DE — a full set for Germany: Shipping, Tracking, Returns, Pickup, Postnumber, and Private Shipping.
- DHL Freight — Price Quote, Shipment Booking, Print, Product, and Time Table for European palletized road freight.
- DHL Global Forwarding — Shipment Booking, Shipment Label, Shipment Status, and a v2 tracking API that returns emissions and routing data.
Tagged areas include Freight, Logistics, Shipping, eCommerce, and Tracking.
What’s interesting
DHL’s API design is organized by division, not by verb. There are separate authentication endpoints for DHL eCommerce Americas, DHL Freight, and Post and Parcel Germany — each division carries its own credentials and its own product catalog. The “Unified” APIs (Location Finder, Shipment Tracking) are the deliberate exception: DHL layers a single interface over divisions that otherwise stay separate.
The tracking story is the most telling. There is a Shipment Tracking Unified API, a push variant that subscribes consumers to status changes, a Global Forwarding v2 tracking API that adds emissions and routing, and division-specific tracking for Parcel DE, eCommerce Americas, and Blue Dart in India. Tracking is not a single feature here — it is a family of surfaces shaped by which network handled the shipment.
DHL also exposes an agentic access artifact (dhl-agentic-access) describing 4 operations, and its published rate limits and three pricing plans are indexed on the network. The provider’s domain security summary reports TLSv1.3, HSTS, DNSSEC, and DMARC.
Takeaway
DHL scores in the thin band (composite 33.7) on the network’s quality rubric, dragged by governance and developer-ergonomics facets even as its discoverability sits at 67.5. The gap is instructive: an enormous, real, division-spanning API footprint is not the same as a coherent developer experience. If you are building against DHL, start with the Unified APIs and the Location Finder OpenAPI spec, then descend into the division-specific surfaces you actually need. Browse the full 48-API surface at apis.io/providers/dhl.