Title: SOAP API > REST API = Packstation bug Last modified: August 19, 2025 --- # SOAP API > REST API = Packstation bug * [frauhoelle](https://wordpress.org/support/users/frauhoelle/) * (@frauhoelle) * [9 months, 3 weeks ago](https://wordpress.org/support/topic/soap-api-rest-api-packstation-bug/) * Since switching from the SOAP API to the REST API, it is unfortunately no longer possible to enter Packstation delivery addresses as before. When using the previous input method, the following error message always appears: “Post Number is missing, it is mandatory for ‘Packstation’ delivery.” * When adjusting the fields, the label can be generated correctly, but two shipments have already been returned to us with the note: “Unfortunately, delivery of the shipment is not possible as it does not comply with our shipping conditions.  The shipment will be returned to the sender.” We just found out that the field“ Adresszeile 2” has completely been removed on the label?! * ![](https://i0.wp.com/www.frauhoelle.com/wp-content/uploads/2025/08/Unbenannt- 1.jpg?ssl=1) * ![](https://i0.wp.com/www.frauhoelle.com/wp-content/uploads/2025/08/Unbenannt- 12jpg.jpg?ssl=1) * How exactly must the details for shipping to a Packstation be entered in the  new REST API in order to ensure both successful label generation and delivery? - This topic was modified 9 months, 3 weeks ago by [frauhoelle](https://wordpress.org/support/users/frauhoelle/). - This topic was modified 9 months, 3 weeks ago by [frauhoelle](https://wordpress.org/support/users/frauhoelle/). Viewing 3 replies - 1 through 3 (of 3 total) * Plugin Author [Saleem Summour](https://wordpress.org/support/users/sal4sup/) * (@sal4sup) * [9 months, 3 weeks ago](https://wordpress.org/support/topic/soap-api-rest-api-packstation-bug/#post-18608101) * Hi [@frauhoelle](https://wordpress.org/support/users/frauhoelle/), * With the switch to the REST API, Packstation addresses must be entered in a very specific way. If any part is in the wrong field, DHL may still generate the label but will reject it during processing. Please make sure the address is filled like this: - **Name:** Recipient’s full name - **Postnummer (customer ID):** Must be filled in the dedicated _Postnummer_ field - **Street:** `Packstation` - **House number:** The 3-digit Packstation number (e.g. `104`) - **Postcode & City:** The Packstation’s postcode and city - **Country:** Germany * **Example:** Max MustermannPostnummer: 1234567890Street: PackstationHouse number: 104Postcode/City: 50667 KölnCountry: DE * Important: Do **not** place the Postnummer in “Address line 2” or “Company”. The REST API ignores that and DHL will return the shipment. It must go into the** Postnummer field**. * The “Adresszeile 2” line on the label is no longer printed with REST, that’s expected. The Postnummer is transmitted in its own field, even if you don’t see it as a separate line on the label. * To avoid mistakes, we strongly recommend using our **Location Finder** in the checkout. It will auto-fill the correct Packstation address fields, including postcode and city, so you don’t have to guess. * This setup ensures the label is accepted by DHL and delivery to the Packstation works without returns. * Thread Starter [frauhoelle](https://wordpress.org/support/users/frauhoelle/) * (@frauhoelle) * [9 months, 3 weeks ago](https://wordpress.org/support/topic/soap-api-rest-api-packstation-bug/#post-18608213) * Hey [@sal4sup](https://wordpress.org/support/users/sal4sup/), * Thanks for your help! * I understand the issue and the new guidelines, but neither in the frontend nor in the backend does a “Postnummer” field appear in my WooCommerce shop system. See the screenshot from my backend: * ![](https://i0.wp.com/www.frauhoelle.com/wp-content/uploads/2025/08/Unbenannt- 1.jpg?ssl=1) * So am I supposed to make any other code/settings changes on my own to see this field (and my customers during checkout process)? * Tanja * Plugin Author [Saleem Summour](https://wordpress.org/support/users/sal4sup/) * (@sal4sup) * [9 months, 2 weeks ago](https://wordpress.org/support/topic/soap-api-rest-api-packstation-bug/#post-18616412) * Hi [@frauhoelle](https://wordpress.org/support/users/frauhoelle/), * You don’t need to add any custom code — the Postnummer field is built into the plugin. It only becomes visible when the Address Type = DHL Packstation option is used. * In the frontend (checkout): Once the customer selects _DHL Packstation_, the Postnummer field will appear and is mandatory. Here’s a screenshot showing exactly where it shows up at checkout: * ![](https://i0.wp.com/i.ibb.co/ZRrgsppy/Screenshot-2025-08-27-at-21-42-36-Short- Code-Checkout-DHL-QA.png?ssl=1) * In the backend (order edit page): In the DHL meta box, if you set the Address Type to DHL Packstation, the Postnummer field will also be available for you to fill before creating the label. * No further settings or code changes are required — just make sure **Location Finder** is enabled in the plugin settings. That way, customers can search and select their Packstation and the fields (Street = Packstation, House number = Packstation number, Postnummer, Postcode, City) are all auto-filled correctly. * This setup ensures REST API labels are valid and DHL accepts the shipment without returns. Viewing 3 replies - 1 through 3 (of 3 total) The topic ‘SOAP API > REST API = Packstation bug’ is closed to new replies. * ![](https://ps.w.org/dhl-for-woocommerce/assets/icon.svg?rev=1777040) * [DHL Shipping Germany for WooCommerce](https://wordpress.org/plugins/dhl-for-woocommerce/) * [Support Threads](https://wordpress.org/support/plugin/dhl-for-woocommerce/) * [Active Topics](https://wordpress.org/support/plugin/dhl-for-woocommerce/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/dhl-for-woocommerce/unresolved/) * [Reviews](https://wordpress.org/support/plugin/dhl-for-woocommerce/reviews/) * 4 replies * 2 participants * Last reply from: [Saleem Summour](https://wordpress.org/support/users/sal4sup/) * Last activity: [9 months, 2 weeks ago](https://wordpress.org/support/topic/soap-api-rest-api-packstation-bug/#post-18616412) * Status: not resolved