Use the DHL Express MyDHL API to retrieve service and product capabilities for an origin-destination pair before booking a shipment
domain: developer.dhl.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using HTTP Basic Auth with your DHL API key and secret as username and password in the Authorization header
GET /mydhlapi/products with query params originCountryCode, originPostalCode, destinationCountryCode, destinationPostalCode, weight, and plannedShippingDateAndTime
Parse the products array in the response; each element contains a productCode, productName, deliveryCapabilities.estimatedDeliveryDateAndTime, and breakdown of pricing
Filter products by desired transit time or service feature flags such as deliveryCapabilities.totalTransitDays
Use the selected productCode when constructing the POST /mydhlapi/shipments booking request body
Validate that the origin-destination pair supports the desired service level before committing to a booking, especially for remote or restricted areas
Known gotchas
The plannedShippingDateAndTime must be in ISO 8601 format with timezone offset; DHL will reject requests with a naive datetime string
Not all productCodes are available for all account configurations; contact DHL to enable specific products if the endpoint returns an empty products array unexpectedly
Weight and dimensions affect which products are returned; omitting dimensions for a large package may return product options that would be rejected at the booking step
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?