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

# Introduction

> Build a hotel's full direct booking experience

The Booking Engine API powers a hotel's direct booking funnel from end to end. Through a single session, you create a search context, return hotel, room, and rate availability, build a basket, quote it, and confirm a booking, with descriptions, promotions, loyalty, and sales terms available across the funnel.

The Booking Engine API is **stateful**: you open a session, carry its identifier across calls, and update the search context, filters, and display options as the guest moves through the funnel.

## How the funnel works

The funnel runs as a connected sequence of steps:

### 1. Create a session

Open a session with the search context: dates, guests, and an optional promo code. The API returns a `sessionId` that you carry on every later call and that holds the basket and context through the funnel.

### 2. Search

With the session open, find the hotels, rooms, and extras that match its context. Refine the results with the filter and sort endpoints (location, budget, rating, and amenities) as the guest narrows their choice.

### 3. Describe

For everything the guest sees, pull the descriptions of the rates, rooms, and hotels: text, pictures, amenities, and policies. These change rarely, so cache them to keep the interface fast.

### 4. Build a basket

When the guest settles on an offer, add the room and any extras to the basket. It holds their selection until you quote it.

### 5. Quote

Quote the basket for its current price and conditions, and fetch the sales terms to display to the guest. When the guest accepts the quote, the **Accept a quote** response returns a `redirectionUrl` to the payment page.

### 6. Payment

Once the guest is on that page, they enter their card and pay. Payment is hosted and handled by D-EDGE, so you never touch card details.

### 7. Confirmation

Once paid, the guest returns to the booking confirmation. It can be served by D-EDGE, or by the hotel's own website when the **Hotel Domain** feature is enabled.

## Get started

> **[Quick start](/booking-engine-api/get-started/quick-start.md)**
>
> Create your first session and run your first call in a few minutes.

> **[Reference](/booking-engine-api/build/reference/session/post-session.md)**
>
> Every endpoint, grouped by stage of the funnel.

> **[Best practices](/booking-engine-api/build/best-practices.md)**
>
> Patterns to build the funnel responsibly and run reliably at scale.

> **[Use cases](/booking-engine-api/resources/use-cases/conversational-booking-agent.md)**
>
> Six patterns, from conversational agents to branded confirmation pages.


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