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

# Requests

> REST across the journey, with the session in the path

The Gift Shop API accepts JSON requests over HTTPS only. Calls over plain HTTP are rejected. Every request must carry the `X-API-KEY` header, as described on the [Authentication](/gift-shop-api/build/guidelines/authentication.md) page.

## Methods

The API follows REST conventions across the journey:

| Method | Use |
| - | - |
| `GET` | Read the session, configuration, categories, cart, and order |
| `POST` | Create a session, search products, add a cart item, confirm the cart |
| `PUT` | Update the session or a cart item |
| `DELETE` | Remove a cart item or empty the cart |

## Session identifier

Every call after session creation carries the `sessionId` in the path, for example `/v1/{sessionId}/cart`. Create a session first with `POST /v1/Session`, then reuse its identifier for the rest of the journey. The identifier is a UUID.

## Headers

| Header | Value |
| - | - |
| `Content-Type` | `application/json` (for `POST` and `PUT`) |
| `X-API-KEY` | Your API key, see [Authentication](/gift-shop-api/build/guidelines/authentication.md) |

## Idempotency

Read calls (`GET`) are safe to retry: they never change state. `PUT` and `DELETE` calls are idempotent while the session is `Pending`: repeating them leaves the cart in the same state. Once the session is paid, the cart no longer accepts changes. `POST` calls are **not** idempotent: retrying **Add a cart item** can duplicate the item, so retry it only when you know the previous call did not reach the server.


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