Packeta feed update guide
In order to provide better services and maintain compatibility, older versions of the Packeta feed will stop working on June 1, 2025. We strongly recommend updating to the latest version to ensure continued functionality.
This guide outlines all the necessary steps to update your implementation.
How to identify unsupported version
To ensure you're using the correct feed source, review your implementation. If it relies on any of the feed data sources listed below, you must update to the latest version (v5). Otherwise, your implementation will stop working on June 1, 2025.
| Version | Data format | Source |
|---|---|---|
| v1 | XML | https://www.zasilkovna.cz/api/v1/__API_KEY__/branch.xml |
| v1 | JSON | https://www.zasilkovna.cz/api/v1/__API_KEY__/branch.json |
| v2 | XML | https://www.zasilkovna.cz/api/v2/__API_KEY__/branch.xml |
| v2 | JSON | https://www.zasilkovna.cz/api/v2/__API_KEY__/branch.json |
| v3 | XML | https://www.zasilkovna.cz/api/v3/__API_KEY__/branch.xml |
| v3 | JSON | https://www.zasilkovna.cz/api/v3/__API_KEY__/branch.json |
If you're using a third-party solution, it is essential to share this information with your supplier or service provider. Providing these details will help them ensure that the solution is properly integrated and functioning as intended.
While feed v4 is not supported, this change will not affect its functionality. However, it is still recommended to migrate to the latest version (v5) to ensure long-term compatibility and access to new features.
Critical: Update to feed v5
The versions above are deprecated and require updating to v5 for continued functionality. Feed v5 is divided into multiple parts, each providing different types of services and delivering data only in JSON format.
| Version | Data format | Contains | Source |
|---|---|---|---|
| v5 | JSON | Pick-up points | https://pickup-point.api.packeta.com/v5/__API_KEY__/branch/json |
| v5 | JSON | Z-BOXes | https://pickup-point.api.packeta.com/v5/__API_KEY__/box/json |
| v5 | JSON | Carriers | https://pickup-point.api.packeta.com/v5/__API_KEY__/carrier/json |
Unlike previous feed versions, feed v5 differs in its structure and format.
The endpoints no longer end with branch.json but with branch/json.
When requesting feed, always use the API Key instead of the API Password. Using an API Password will cause errors, and no data will be retrieved.
How to update
- If you are using Packeta Pick-up Point delivery:
- Update the feed source URL to the latest version (v5) that includes Packeta Pick-up Points.
- For detailed instructions, refer to the PUDO Delivery - Packeta PUDOs.
- If you are using Packeta Z-BOX delivery:
- Update the feed source URL to the latest version (v5) that includes Packeta Z-BOXes.
- For detailed instructions, refer to the PUDO Delivery - Packeta PUDOs.
- If you are using Home Delivery service:
- Update the feed source URL to the latest version (v5) that includes a list of carriers.
- For detailed instructions, refer to the Home delivery - Carriers.
- If you are using Carriers' Pick-up point delivery:
- No changes are required for your current setup. However, ensure that you are consuming the correct feed containing the list of carriers.
Version differences
*Click to view the full image, or you can download the Excel file.
Why old feeds are being removed
We are discontinuing the older versions of feeds to improve service quality and performance, which are our top priorities. Below, we explain the reasons behind this decision.
Service quality
Older feed versions (v1–v3) were designed before services like Packeta Z-BOXes or modern carrier solutions were introduced. These older versions were deprecated and unsupported by the time we implemented these new services.
- Key points
- Z-BOXes: Introduced with v4, allowing clients access to box services. Versions v1–v3 lack this feature.
- Carriers: Carrier-related system integrations have evolved, and earlier feeds (v1–v3) no longer deliver reliable or correct information.
- Contacts: Contact details are intentionally excluded from all data feeds as we believe this information is better managed through other channels.
Refer to the table below for a summary of what each feed version includes and the reasoning behind our decision:
| Version | Pick-up points | Z-BOXes | Carriers | Contacts |
|---|---|---|---|---|
| v1 | YES | NO | NO | NO |
| v2 | YES | NO | Not reliable | YES |
| v3 | YES | NO | Not reliable | YES |
| v4 | YES | YES | YES | NO |
| v5 | YES (separate feed) | YES (separate feed) | YES (separate feed) | NO |
Performance
With each version, new features and parameters have been added, leading to larger feed sizes. Currently, clients can generate feeds of all versions in both XML and JSON formats, which can multiply storage and transfer requirements.
For reference, the table below shows how feed sizes have grown over time:
| Version | Average size (MB) |
|---|---|
| v1 | 18 |
| v2 | 23 |
| v3 | 28 |
| v4 | 48 |
| v5 | 15, 16, 1 |
*Size can differ based on your settings and current network capacity.
Discontinuing older feed versions improves quality and reduces system load resulting from large, outdated feeds. We encourage migrating to v5 for its robust performance and the inclusion of all relevant information.
Contact us
If you have any questions, you can contact your Sales Manager. The contact email is available in the client section under User Support.
Additionally, our integrations team at integrations@packeta.com is ready to assist you.