Common issues
This section describes the most common errors you may encounter when using the Packeta API. Each listed topic includes the API error message, short explanation of the topic and recommended resolution steps.
Understanding the <eshop> parameter
Description
The <eshop> parameter identifies the sender (e-shop) of a packet. It is linked to the sender configuration in the client section and is used for correct packet processing and invoicing.
Fill the <eshop> parameter with the configured Sender Indication from the client section. For example, use a store identifier such as the e-shop name and country, rather than a website URL or domain.
Error message
If an invalid or non-existing Sender Indication is provided in the <eshop> parameter when creating a packet, the API returns the following response.
- Response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>eshop_id</name>
<fault>Order nr. 12345: Sender is not given. Please choose a sender.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
- Verify that the sender is configured in Client section → Senders.
- Use the configured sender Indication as the value of the
<eshop>parameter. - Check for typos, empty spaces or invalid values.
- If multiple e-shops are supported, ensure the correct Indication is sent for each packet
Client account not approved
Description
Your client section account was not yet approved for creating packets. Until the onboarding process is completed, packet creation is disabled. Please reach out to the sales support team or your account manager.
Error message
- Packet response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>user_id</name>
<fault>Order nr. 123456: The client account is not approved for posting parcels.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
- Complete the account setup process following the setup guide
- Contact your sales representative or sales department to request account approval.
Cash on delivery currency issues
Description
We strongly recommend specifying both the currency and the packet value for Cash on Delivery (COD) packets. If a currency is not provided, the value is automatically interpreted in the currency of the destination country.
A packet value of 500 without a specified currency will be interpreted differently depending on the destination:
- Delivery to Czechia → 500 CZK
- Delivery to Hungary → 500 HUF
To avoid ambiguity and unexpected values, always specify the currency explicitly.
If you use currency conversion configured in the Client section → Currency Conversion, you can send the value in the target currency defined for the conversion. You can set up the conversaion following the guide.
To receive COD payouts in a specific currency, you must have a bank account configured for that currency in your Client section → Billing addresses. If you call <createPacket> with <currency> for which no corresponding bank account is configured, the request will fail with the error shown below.
Error message
- Response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>currency</name>
<fault>Order nr. 12345: You entered an unauthorized currency. You can either enter the currency of the country to which the parcel is being delivered; or if you have set a currency conversion while entering the parcel (not while sending money), then you can also enter the currency to which you are converting.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
- If you use currency conversion, make sure the currency is enabled in your Client section → Currency conversions.
- Correct any invalid currency codes or typos
Packet/COD value exceeds the allowed limit
Description
Every destination has maximum allowed values for the packet insurance and the COD amount. Requests exceeding these limits are rejected.
Error message
- Packet response
- COD response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>value</name>
<fault>Order nr. 12345: Parcel can not be insured to such a high value according
to our conditions.</fault>
</fault>
</attributes>
</detail>
</response>
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>cod</name>
<fault>Order nr. 12345: According to our Conditions, COD of such a value can not be entered.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
Reduce the packet value or COD amount so that it complies with Packeta's limits and Terms & Conditions.
Accepted cash on delivery values
Description
Cash on Delivery values must respect the smallest cash denomination accepted in the destination country.
- CZK → whole numbers only
- HUF → multiples of 5
Error message
- Packet response CZK
- Packet response HUF
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>cod</name>
<fault>Order nr. 123456: Unacceptable value for CZK currency. Please fill in a whole number.</fault>
</fault>
</attributes>
</detail>
</response>
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>cod</name>
<fault>Order nr. 123456: Unacceptable value for HUF currency. Please fill in multiple of five (number ending on 0 or 5).</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
Adjust the <cod> value to match the accepted denomination of the destination currency.
Handling country codes in phone numbers
Description
If a phone number does not include a country code, we attempt to interpret it as a phone number from the destination country. For example, if you send a shipment to Hungary and provide the phone number 123456789, we will interpret it as +36123456789.
See Phone number formats for supported phone number structures.
Error message
- Packet response HUF
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>phone</name>
<fault>Order nr. 123456: Phone number is not in valid format, dialing code is required. Please either correct it or delete it.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
- Use a valid international phone number.
- Include the country dialing code when required.
- Verify the format against the supported phone number formats.
Custom barcode not enabled
Description
Packeta generates packet barcodes automatically. Custom packet barcodes are not publicly available.
Error message
- Packet response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>barcode</name>
<fault>Č. ob. 123456: Zadané trasovací číslo zásilky není z rozsahu přidělovaného klientům.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
Remove the <id> parameter and allow Packeta to generate the barcode automatically.
Customs declaration issues
Description
The packet is missing required customs declaration data or contains invalid customs information in the field described in the error message.
Error message
- Packet response
<response>
<status>fault</status>
<fault>PacketAttributesFault</fault>
<string>Failed to validate attributes. See detail.</string>
<detail>
<attributes>
<fault>
<name>phone</name>
<fault>Order nr. 123456: This Carrier requires a valid cellphone number of the destination country.</fault>
</fault>
<fault>
<name>attributes.attributes.items</name>
<fault>Order nr. 123456: No customs declaration item is filled in. The customs declaration must contain at least one item.</fault>
</fault>
<fault>
<name>attributes.attributes.ead</name>
<fault>Order nr. 123456: Please fill in this entry.</fault>
</fault>
<fault>
<name>attributes.attributes.deliveryCost</name>
<fault>Order nr. 123456: Please fill in this entry.</fault>
</fault>
<fault>
<name>attributes.attributes.invoiceNumber</name>
<fault>Order nr. 123456: Please fill in this entry.</fault>
</fault>
<fault>
<name>attributes.attributes.invoiceIssueDate</name>
<fault>Order nr. 123456: Please fill in this entry.</fault>
</fault>
</attributes>
</detail>
</response>
Resolution
Verify all customs declaration fields and follow the customs declaration guide before creating the packet.
Single field for the first and last Name
If your system does not store the first name and last name separately, you can send the full name in the name field.
We will attempt to split the full name into first name and surname automatically. However, the result may not be accurate for all name formats.
Single field for the street and house number
If your system does not store the street name and house number separately, you can send the full address in the street field.
We will attempt to split the street name and house number automatically. However, we cannot guarantee accurate results for complex addresses, such as those containing apartment, unit, or building numbers.
Some carriers require separate address fields and validate them during packet creation. If the address cannot be processed correctly, the packetCourierNumber may return an error. See example of the error message from HR Overseas HD.
Modifying Exported Orders
It is not possible to modify existing orders using our API.