Skip to main content
The Gift Shop API returns JSON. The exact body shape depends on the status code.

​
Content type

​
Error format

Errors follow the problem details format (RFC 7807). This differs from the Booking Engine API’s Message/Code shape, so handle each API’s errors separately if you integrate both.
​
string
A URI reference that identifies the problem type. On validation errors it points at the matching RFC 9110 status section.
​
string
Short, human-readable summary of the problem.
​
integer
The HTTP status code.
​
string
Human-readable explanation specific to this occurrence. Absent on validation errors.
​
string
A URI reference that identifies this specific occurrence. Absent on validation errors.
​
object
On validation errors only: one entry per offending parameter, with the reasons it was rejected.
​
string
On validation errors only: the identifier of the failing call. Log it; it is the fastest way for the partnership team to find your request.

​
Response codes

​
200 OK and 201 Created

The request was processed successfully. The body depends on the endpoint: a session identifier, the configuration, products, the cart, or the order. Add a cart item returns 201 with the identifiers of the created items; every other call that returns a body answers 200, including Create a new session.

​
204 No Content

The request succeeded and there is nothing to return: updating the session, updating a cart item, removing an item, or emptying the cart. Reading the session’s shopper before one is attached also returns 204.

​
400 Bad Request

The request failed validation. The problem details body says which parameters are invalid or missing; validation failures also carry an errors map with one entry per offending parameter. Fix the request before retrying.

​
401 Unauthorized

The X-API-KEY header is missing, invalid, or does not give access to the operation. See the Authentication page.

​
403 Forbidden

Declared on the two localisation reads only (Get country names and Get phone codes); no other operation returns it. Those two reads also declare their 404 with no body, unlike the rest of the API.

​
404 Not Found

The sessionId does not match an active session: it may have expired, or never existed. Create a fresh session and rebuild the guest’s cart. This differs from the Booking Engine API, where an expired session returns 400. On Get the gift shop configuration, a 404 has a second possible cause: no configuration exists for the session’s owner. When a freshly created session still returns 404 on that call, check the hotelId and groupId you open the session with instead of recreating it.

​
5xx

A 5xx response signals an issue on the D-EDGE side. These errors are usually transient. Retry safe GET calls with exponential backoff. If a 5xx persists, contact us.