> ## 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.

# Changelog

> Updates to the Booking Engine API

This changelog tracks public-facing changes to the Booking Engine API: new endpoints, breaking changes, deprecation notices, and behaviour adjustments worth knowing about.

**21 September 2026**

Enum values, response codes

## Enum values described, one status per outcome

Enumerated fields such as payment types and error codes carry a description of their values: open `defaultPaymentType` on [Get a quote for the basket](/booking-engine-api/build/reference/basket/get-quote.md) to read what each option means. The calls that change state answer `204 No Content` with no body, and [Provides an ongoing promotion](/booking-engine-api/build/reference/promotion/get-promotion.md) answers `204` when the hotel runs no promotion. Check that your client treats `204` as a success.

**3 June 2026**

Public release

## Initial public documentation

The Booking Engine API joins the portal. It powers a hotel's full direct booking funnel through a single stateful session:

* **Session**: create a session and update its search context, filters, display, and sort order.
* **Search**: find hotels, rooms, and extras matching the session context.
* **Description**: read descriptions for rates, rooms, extras, and hotels.
* **Basket**: add rooms and extras, then quote, accept, and read sales terms.
* **Booking**: create a booking access token and read a booking confirmation.
* **Loyalty, Promotion, Configuration, Resources**: supporting endpoints for the funnel.


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