Contents

UBsend APIs

Tracking events

Parcelshop

Customs

Booking

 

Earlier versions of API Documentation can be found here

Integration Troubleshooting

Invalid service parameter, Service ‘PSD’

Status Code: 400

You entered a parcel shop ID and got the following response.

Use our Pudo shop finder to identify a valid parcel shop ID

Unauthorized access for clientId=[XXXX]

You used a bearer token to authorize for booking a shipment and got the following response.

Check if the following is the correct:

  • Client ID for the shipment request
  • User email and password are the right ones for the environment (client ID)

If you cannot find any mistakes, reach out to your technical contact in your implementation project or to our Support team

400 Shipment submit failure: Shipment booking failed. Internal service call failed.

Exceeded maximum length in address or name fields

  • Remove unnecessary parts of the addresses or first and last names
  • Use additional fields for extensions such as “addressLine2” and/or “company”

Bad Request: Error 1:- Error Path:/dataElement/cPAN/addresses/recipient/street1;

Exceeded maximum length in address or name fields

  • Remove unnecessary parts of the addresses or first and last names
  • Use additional fields for extensions such as “addressLine2” and/or “company”

Error Message: Value is longer than maximum length

Exceeded maximum length in address or name fields

  • Remove unnecessary parts of the addresses or first and last names
  • Use additional fields for extensions such as “addressLine2” and/or “company”

Carrier [enum] is not available for the active client [XXXX]

You tried to use a certain carrier or product and got the following response.

Make sure that you are using the products and carriers that have been agreed with the UBSend team. If everything is correct, please reach out to your technical contact in your implementation project to review the carrier/product activation.

Carrier or Product specific Errors

Pickup Products

  • Remember to add pickup information into the booking request

  • For testing, pickup time must be later than now for pickup products

Example:

},
"collectionInfo": {
"type": "PICK_UP",
"date": "2026-03-06",
"preferredTime": ,

Parcelforce

You tried to book a Parcelforce product in your Staging environment and got the following error message:

"status": 501,
"error": "Not Implemented",
"message": "Couldn't find a suitable HUB configuration for postal code 'London West Depot' and date '2026-01-20'"

Solution:

We are regularly updating hub addresses in our Staging environment but this one might be most recently changed/deleted by the carrier. Please reach out to your technical contact in your implementation project or to our Support team

GLS PUDO Shop Finder

If you have trouble locating parcel shops it may be due to the country specification in the carrier enum

Solution:

For GLS shipments in different countries, use the “GLS_INT” as the carrier parameter instead of country-specific parameters, such as “GLS_DK”.

GLS Czech Republic

You tried to book a Pudo product with GLS in Czech Republic and got the following response.

Error example:

"status": 400,
"error": "Bad Request",
"message": "GLS CZ Parcel Shop product requires a valid Czech mobile phone number for the recipient.",
"path": "/shipments/label",

Solution:

Czech mobile phone numbers have a specific length and number prefix. Refer to the mobile phone list in Wikipedia.

Deutsche Post

Packstation pickup booking errors

Solution:

For Deutsche Post products that require pickup from a “Packstation” (e.g., for the enums DEUTSCHE_POST_DE_PAKET, DEUTSCHE_POST_DE_LOCKER), it is mandatory to enter your customer number in field “deliveryInstructions”.