REST API with OAuth2/JWT
Secure requests with OAuth2 and JWT bearer tokens. Unified API calls reduce integration overhead across shop, ERP, and WMS connections.
Use this page as your central overview for carrier connections, platform integrations, API capabilities, and routing decisions for DACH e-commerce operations.
Shippinglabel links your e-commerce stack with leading parcel carriers. Create shipping labels via API or web app, run batch workflows, and control carrier-specific services in one process.
A multi-carrier shipping API is a technical interface that lets merchants connect multiple shipping providers through one unified integration model. Instead of maintaining separate flows, field mappings, and authentication logic per carrier, shipping runs through one consistent API path.
For operations teams this means less manual effort, clearer workflows, and faster label output. For developers this means a stable architecture with OAuth2/JWT authentication, clear endpoints, and better maintainability when fulfillment volume grows.
Shippinglabel is built for DACH e-commerce. Connect carriers such as DHL, Hermes, DPD, GLS, or UPS to your shop landscape, synchronize orders via inbound integrations, and control shipping centrally instead of platform by platform.
The following capabilities are already available in production and cover key requirements for fulfillment, automation, and carrier orchestration.
Secure requests with OAuth2 and JWT bearer tokens. Unified API calls reduce integration overhead across shop, ERP, and WMS connections.
Create high volumes of shipping labels in one step via `POST /v2/shipments/bulk`. Ideal for peak periods, marketplace volume, and daily mass fulfillment runs.
Support multiple parcels per order in one shipment flow. Complex shipping cases stay structured, with clear label output per parcel.
CashOnDelivery is available for multiple carriers (including DHL, GLS, Hermes, UPS, PostAT, DPD). This supports DACH-specific payment and delivery patterns directly in shipping logic.
This matrix provides practical orientation for common e-commerce use cases. It does not replace contract-level carrier checks, but it gives a strong first routing baseline.
| Shipping scenario | DHL | Hermes | DPD | GLS | UPS |
|---|---|---|---|---|---|
| B2C national | Very strong standard network and high end-customer acceptance. | Cost-focused B2C setup, suitable for high parcel volumes. | Strong national coverage with balanced B2C/B2B usage. | Reliable for standardized parcel operations. | Strong option, often used for higher-value shipments. |
| B2C international | Broad international parcel options. | Available depending on destination and service profile. | EU-oriented with solid cross-border coverage. | Good fit for EU-near international shipping. | Strong global reach and SLA-driven profiles. |
| Express | Express products can be mapped via DHL Express integration. | Primarily focused on standard delivery. | Express options depend on contract profile. | Limited express orientation by market and contract. | Clear strength in time-critical express scenarios. |
| Bulky / heavy shipments | Possible depending on product and size limits. | Requires checks by parcel dimensions and service profile. | Contract-dependent support for larger formats. | Good for regular parcels; check country constraints. | Strong for more complex parcel and weight profiles. |
This summary highlights key operational differences and helps teams define routing logic by shipment type.
| Criterion | DHL | Hermes | DPD | GLS | UPS |
|---|---|---|---|---|---|
| Core strength | High DACH B2C brand coverage. | Cost efficiency in volume shipping. | Balanced B2C/B2B profile. | Stable execution for standard parcel flows. | International + express + advanced profiles. |
| Typical use case | Standard B2C, domestic and international parcels. | Cost-oriented B2C lanes. | Day-to-day parcel shipping with strong EU options. | Predictable standard shipping cycles. | Time-critical or higher-value shipments. |
| CashOnDelivery | Supported | Supported | Supported | Supported | Supported |
| Multi-piece | Supported | Supported | Supported | Supported | Supported |
Use the links below to dive deeper into specific carrier APIs, platform integrations, and pricing content. This creates a clear hub-spoke structure across commercial search intent clusters.
Short answers to common questions from e-commerce operators, integrators, and technical decision makers.
No. Operations teams benefit directly: faster label workflows, fewer tool switches, and cleaner cross-carrier execution.
Native integrations are available for WooCommerce, Shopware, eBay, Kaufland, and Magento, connected directly to carrier workflows.
Inbound webhooks for order synchronization are supported for eBay, Shopware, Kaufland, and WooCommerce. Outbound status webhooks are currently not part of scope.
Yes. High-volume creation is supported via `POST /v2/shipments/bulk`, so fulfillment teams can stay stable during peak load.
Start with 2-3 core carriers for your main scenarios (for example B2C domestic + international), then expand with rule-based routing for express, COD, and multi-piece cases.
Common questions about connecting shops, marketplaces, and carriers.