Connectors
E-commerce
DHL Parcel Germany
DHL parcel shipping in Germany: shipments and labels, returns, pickups, and manifests
- Signs in with
- Username and password
- Runs on
- Cloud or On-Prem Worker
- Operations
- 14
- Ready-made triggers
- 0
Connect DHL Parcel Germany
- In Neblex open Connect › Connections and click New Connection.
- Search for DHL Parcel Germany and give the connection a clear name.
- Fill in the fields. Secret values are encrypted and never shown again.
- Click Test, then Create Connection.
| Field | What to enter |
|---|---|
| EnvironmentRequired | Post and Parcel Germany production or sandbox host. |
| API keyRequiredSecret | Consumer key of the DHL Developer Portal app, sent as the dhl-api-key header. |
| User nameRequired | Business customer portal (GKP) user name of the partner system. |
| PasswordRequiredSecret | Business customer portal (GKP) password of the partner system. |
Use it in a flow
- Open a flow, open the node library and search for DHL Parcel Germany.
- Drag it onto the canvas and choose an Operation and your connection.
- Map the operation's fields from earlier steps, or click Map with Matt.
- Use Test this step to see what it returns, then save.
To start a flow from DHL Parcel Germany without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if DHL Parcel Germany can send webhooks, a Webhook trigger receives them at its own URL.
Operations
14 operations in 5 groups. Each one is a step you can add to a flow.
Manifests2
Mark shipments as being ready for shippingcreateManifest | POST | Shipments are normally ''closed out'' at a fixed time of the day (such as 6 pm, configured by EKP/account) for the date provided as shipDate in the create call. |
Retrieve daily manifest documentgetManifest | GET | Return the manifest document for the specific date (abbreviated ISO8601 format YYYY-MM-DD). |
Pickup4
Cancels pickup order(s)cancelPickupOrders | DELETE | This operation cancels one (or several) pickup order(s). |
Get order details and statusgetPickupOrders | GET | Retrieve data for specific pick up orders. |
Places a parcel pick up order for a number of parcelscreatePickupOrder | POST | The root ressource to placing orders. |
Return API versiongetPickupApiVersion | GET | Returns the current version of the API as major.minor.patch. |
Returns3
Create a return labelcreateReturnOrder | POST | Creates a return label by given information. |
Get available return locationsgetReturnLocations | GET | The response should be a list of Receiver, each containing the following information |
Return API versiongetReturnsApiVersion | GET | Returns the current version of the API as major.minor.patch. |
Shipments and Labels4
Create one or more shipments and their documents. (This is the primary call of the API.)createShipments | POST | This request is used to create one or more shipments and return corresponding shipment tracking numbers, labels, and documentation. |
Delete one or more shipmentsdeleteShipments | DELETE | Delete one or more shipments created earlier. |
Download PDF documentdownloadLabel | GET | Public download URL for shipment labels and documents. |
Retrieve shipment documents - labels and customs documentsgetShipmentDocuments | GET | Returns documents for existing shipment(s). |
General1
Return API versiongetShippingApiVersion | GET | Returns the current version of the API as major.minor.patch. |