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

> One POST body, plus the layout that shapes the response

The Daily Rates API accepts JSON requests over HTTPS only. Calls over plain HTTP are rejected. Every request is a `POST` and must be authenticated as described on the [Authentication](/daily-rates-api/build/guidelines/authentication.md) page.

## Body

The request body is a single JSON object. It carries the date range, the guest configuration, the `filter` selecting hotels and rate plans, and the `layout` describing which fields to return. Field names, types, and accepted values are documented in the [Reference](/daily-rates-api/build/reference/per-day.md).

| Header | Value |
| - | - |
| `Content-Type` | `application/json` |
| `Authorization` | OAuth-signed, see [Authentication](/daily-rates-api/build/guidelines/authentication.md) |

## Guests

The `guests` array sets the occupancy the API prices. Send at least one item, and one item per combination to price several occupancies in the same request. Each entity in the response repeats the requested combination in its own `guests` field, so you can match it to your request. One call with several combinations is preferable to one call per combination.

Do not derive the price of one occupancy from another: per-person supplements, occupancy-based rates, and meal plans make prices vary with the number of guests.

## Layout

The `layout` field tells the API which properties to compute and return for each entity in the response: availability, prices, restrictions, promotions, articles, and so on. Request only the properties you need: a smaller layout means a smaller response and a faster call.

## Safe to retry

The Daily Rates API is read-only. Calls never modify data on the D-EDGE side. You can safely retry a request without risk of duplication or side effects.


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