Error key | Status code | Action |
|---|
no.access.api | 403 | Your user does not have access to this API. Notify your carrier contact person to update your access |
no.access.shop.id | 403 | Your user does not have access to the shop registered to the order you try to edit. Notify your carrier contact person to update your access |
cannot.find.order | 404 | We can not recognise the shipmentID specified, please check that it is a valid and correct ID |
unable.to.edit.exporter.order | 400 | For some carriers and freight products we do not have the possibility to edit and order after they have registered the order, therefor these orders can not be edited. See flow chart under “use of service” for details. |
order.cancelled | 400 | It is not possible to edit cancelled ordres |
no.changes.in.patch | 400 | The edit order request you are trying to perform does not have any changes from what information is already registered on the order. |
invalid.format.desiredDeliveryDate | 400 | Please check your date format |
order.changes.freightproduct | 400 | The edit order request you have will result in a different delivery method (freight product), and is not possible to perform. This can be for several reasons, maybe the date or address changes are not supported for the existing freight product |
failed.to.parse.request | 400 | Please check your path value, we are not able to recognise the key. Remember this path value is case sensitive |
JsonPatch.format.invalid | 400 | Please check you request format, see valid format in examples above. |
failed.to.map.JsonPatch | 400 | |
distributionDate.must.be.in.future | 400 | Change distribution date. |
error.parcel.final.status | 400 | Parcel has reach a final destination and can not be edited. |
order.exported | 400 | For some carriers and freight products we do not have the possibility to edit and order after they have registered the order, therefor these orders can not be edited. See flow chart under “use of service” for details. |
party.name.required | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
party.name.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
address.required | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
address.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
zipCode.required | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
email.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
phone.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
co.address.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
zipCode.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
postalName.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
countryCode.too.long | 400 | Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation |
error.parcel.under.distribution | 409 | Please see Use of https://jira-di.atlassian.net/wiki/spaces/DIPUB/pages/2177597504/Parcel+Edit+Order+API#Use-of-Service for when parcels can be edited. |
internal.error | 500 | If you receive this error please notify your carrier contact person, and provide the request(s) you try to perform |