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

# Confirm bookings

> D-EDGE acknowledges each booking it has integrated

> [!NOTE]
>
> D-EDGE sends HTTP `POST` requests to the URL you provide, with the XML message as the raw body and the [credentials inside the message](/channel-manager-api/build/guidelines/authentication.md). The hosting model is described in [the introduction](/channel-manager-api/get-started/introduction.md#an-api-that-runs-on-your-endpoints).

Confirm bookings closes the booking loop. Once a booking coming from [Get bookings](/channel-manager-api/build/reference/get-bookings.md) or [Push bookings](/channel-manager-api/build/reference/push-bookings.md) is fully processed in D-EDGE, an asynchronous acknowledgement reaches your endpoint. It carries your booking identifier and the D-EDGE booking reference.

This is the message that tells you a booking is really in. Use it to mark the booking as integrated on your side, and as the trigger for retries: a booking still unconfirmed **15 minutes** after the push is worth pushing again.

## The message we send

**message** `element` *required*

The root element.

**child elements**

**authentication** `element` *required*

Your credentials: a `login` and a `password` attribute, each up to 50 characters. See [Authentication](/channel-manager-api/build/guidelines/authentication.md).

**bookingConfirmation** `element` *required*

The acknowledgement.

**attributes**

**hotelCode** `attribute · string` *required*

The hotel identifier or code on your platform. Maximum 50 characters.

**partnerBookingId** `attribute · string` *required*

Your booking identifier, the `id` of the [booking message](/channel-manager-api/build/reference/booking-message.md). Maximum 20 characters.

**status** `attribute · enum` *required*

The action that was integrated in D-EDGE: `Create`, `Modify`, or `Cancel`.

**crsBookingId** `attribute · string` *required*

The booking reference in D-EDGE.

```xml Request theme={null}
<?xml version="1.0" encoding="utf-8"?>
<message>
  <authentication login="testhotel" password="testpassword" />
  <bookingConfirmation hotelCode="1234" partnerBookingId="EOCFGA"
                       status="Create" crsBookingId="RXHS34" />
</message>
```

## Your response

Answer `200 OK` with the [message envelope](/channel-manager-api/build/guidelines/responses.md): `<success>` when the acknowledgement is recorded, `<warning>` when it is recorded with a reservation. On a refusal, `<failure>` with `3` when the credentials do not match, or `201`, `202`, or `203` when the message could not be read.

```xml Success theme={null}
<?xml version="1.0" encoding="utf-8"?>
<message>
  <success />
</message>
```

```xml Failure theme={null}
<?xml version="1.0" encoding="utf-8"?>
<message>
  <failure type="202" message="InvalidXMLMessage">
    <comment><![CDATA[Missing bookingConfirmation element]]></comment>
  </failure>
</message>
```

> [!NOTE]
>
> Like every message D-EDGE sends, the request can start with a byte order mark. It carries `Content-Type: application/xml; charset=utf-8`, but parse the body whatever the header says. See [Requests](/channel-manager-api/build/guidelines/requests.md).


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