...
Example | Description | |
Username (see Authentication section) | wsfoobar | A valid username. |
Password (see Authentication section) | a-very-very-long-password | A password matching given username. |
shopId | 1234 | All requests are made with respect to a given shop.Ā |
transportSolutionId | 5 | An identifier for a valid transport solution. The transport solution determines how the booked package will be distributed. |
...
The user is a web service user
The user has access to the web serviceĀ for coverage check
The user has access to the specified shop
The shop has access to the specified transport solution
Environments
Consider using the TEST-endpoint while developing your system. By doing this you ensure that your test-data will not pollute any potential external systems.
...
This endpoint requires the user to be authenticated. Refer to the documentationĀ here for more information on how to obtain a valid token to use in your request.Ā
Making a request
| 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. |
Request headers
Key | Value example | Comment |
Authorization | Bearer "SECRET_WS_TOKEN" | See authentication on how to obtain a token |
Content-Type | application/json |
...