Versions Compared

Old Version 1

changes.mady.by.user Michal Matovcik

Saved on

compared with

New Version Current

changes.mady.by.user Marie-Luise Faatz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The user is a web service user

  • The user has access to the web service “Parcel Wanted API”The user is in at least role of following roles: PARCEL_ADMIN, PARCEL_QUALITY_ADMIN, PARCEL_SHOP_ADMINservice for booking

  • The user has access to the shop the parcel (trackingReference) is connected to

...

Info

  • Clients using this API should not fail if new optional fields are added to the API. If a new field is added to the request or response on a later stage, existing clients should handle this in a way such as they just ignore the field.

  • The trackingReference must be already known to the system (created by e.g. the Parcel Booking API)

  • (error) Do not share personal or sensitive information in this API.

...

URL Path Param

Name

Type

Example

Max LenghtLength

Mandatory

Description

trackingReference

string

(00)370724760010119754

35

(tick)

Tracking reference for the item, typically a SSCC gs1 code.

...

Request

Code Block
{
    "wanted": "false"
}

Error handling

API requests that result in errors will return an appropriate HTTP status code to help you identify the type of error. You can use the table below to understand what each code means. og search online with the HTTP status code. The HTTP error keys used are based on the standard, and therefore available online (Tips to search “HTTP code XXX”)

...