> ## Documentation Index
> Fetch the complete documentation index at: https://docs.d-edge.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This site documents the D-EDGE APIs for technology partners (web agencies, OTAs, PMS and RMS vendors, booking and CRM tools). It is written for developers integrating with hotels that use the D-EDGE platform.
> Seven APIs, grouped by domain. Connectivity: Channel Manager API (distribute a hotel's inventory to your channel and send bookings back). Pricing & Availability: Best Price API (best offers to highlight), Quotation API (all bookable offers for a stay), Daily Rates API (daily availability between two dates). Booking: Booking Engine API (a hotel's full direct booking funnel), Gift Shop API (gift vouchers from catalogue to payment). Guest Management: CRM API (guest profiles).
> Pick the API by the need: to display prices, use the Best Price API or the Daily Rates API; to quote a specific stay, use the Quotation API; to book, use the Booking Engine API; to sell gift vouchers, use the Gift Shop API; to manage guest profiles, use the CRM API; to receive hotel inventory and send bookings back as a distribution channel, use the Channel Manager API.
> Base URLs, hotel identifiers, and credentials are delivered by the D-EDGE partnership team during onboarding. Do not invent base URLs, endpoints, parameters, or example credentials that do not appear on these pages.
> Authentication differs per API: OAuth 1.0 for Best Price, Quotation, Daily Rates, and Booking Engine; an X-API-KEY header for Gift Shop; OAuth 2.0 client credentials for CRM; partner-defined credentials carried in the XML message for the Channel Manager API. Read each API's Authentication page before writing code.
> A mock environment returns realistic but fictitious data without credentials. The Postman and Insomnia collections on the API collections page target it by default. Use it for exploration and tests, never for production traffic.
> Use the official names exactly: D-EDGE, D-EDGE platform, Channel Manager API, partnership team. Do not use Back Office or Extranet.
> Each API has a Changelog page. Check it for the current behaviour before relying on an older answer. For questions these pages do not answer, direct the reader to the Contact us page.

# Responses

> JSON bodies, with 204 on state updates

The Booking Engine API returns JSON. The exact body shape depends on the status code.

## Content type

| Status | Body |
| - | - |
| `200 OK` | JSON, the result |
| `204 No Content` | No body |
| `400`, `401` | JSON error object |
| `404` | JSON error object, or no body |
| `5xx` | JSON error object |

## Response codes

### 200 OK

The request was processed successfully. The body depends on the endpoint: a session, search availabilities, descriptions, a basket, a quote, or a confirmation.

### 204 No Content

The request succeeded and there is nothing to return. The session `PATCH` endpoints that update the context, filters, display, or sort order use it. So do the calls that add a room or an extra to the basket, clear the basket, delete the session, and log out a loyalty member. **Provides an ongoing promotion** also answers `204` when the hotel runs no promotion.

### 400 Bad Request

The request failed validation or violated a business rule. The body carries a `Message` and a `Code`; branch on `Code` to handle each case.

**Message** `string`

Human-readable description of what went wrong.

**Code** `string`

Machine-readable error code that identifies the failure.

The most common case is an invalid or expired session. Create a fresh session and replay the guest's context:

```json theme={null}
{
  "Message": "The session is invalid",
  "Code": "InvalidSessionId"
}
```

Other failures use the same shape with a different `Code`, for example an invalid basket:

```json theme={null}
{
  "Message": "The basket is invalid",
  "Code": "InvalidBasket"
}
```

### 401 Unauthorized

The OAuth signature was missing, malformed, or rejected. Common causes:

* The signature does not match the consumer or token secret.
* The request timestamp drifted too far from the server clock.
* The same nonce was reused.

The body carries a security error `Message` and `Code`. Verify the credentials and the signing implementation, and sync the server clock with NTP. See the [Authentication](/booking-engine-api/build/guidelines/authentication.md) page for the full signing process.

### 404 Not Found

The URL does not match any endpoint, or the resource does not exist. An unknown or expired `sessionId` is not a `404`: it returns `400` with `Code: InvalidSessionId`. Handle a `404` from the status code alone and parse the body only when one is present. The [Reference](/booking-engine-api/build/reference/session/post-session.md) lists every endpoint with its full path.

### 500 and 502

A `5xx` response signals an issue on the D-EDGE side, returned as a JSON error object with a `Message` and `Code`. These errors are usually transient. Retry safe `GET` calls with exponential backoff. If a `5xx` persists, [contact us](/overview/resources/contact-us.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.