Declare and ship a Dangerous Goods (hazmat) international parcel through the DHL Express MyDHL API
domain: developer.dhl.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the DHL Express account number has Dangerous Goods approval and a signed contract covering the specific content/service combination before attempting the shipment
Determine the correct DangerousGoods ServiceCode and ContentId for the item classification
Include the ServiceCode and ContentId values in the shipment request body alongside standard shipment fields
Submit the shipment request and confirm the response does not flag a compliance hold
Apply any required physical hazard labels and documentation to the package before hand-off, since API acceptance does not replace physical compliance
Retain the shipment confirmation as evidence of compliant tender in case of a facility-level DG inspection
Known gotchas
Shipments tendered without prior account-level Dangerous Goods approval and contract sign-off are stopped at the DHL facility even if the API request itself succeeds
The correct ServiceCode/ContentId pairing is content- and destination-specific; using the wrong pair can cause a rejection or a compliance hold after tender
API acceptance of a DG shipment does not waive the shipper's responsibility for correct physical packaging, labeling, and documentation under applicable dangerous goods regulations
Give your agent this knowledge — and 15,500+ 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?