> ## 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 Daily Rates API

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

**28 September 2026**

Guidelines

## Guests in Per day requests

The [Requests](/daily-rates-api/build/guidelines/requests.md#guests) guideline explains how `guests` drives prices and how to price several occupancies in one call.

**1 September 2026**

Reference

## Every field of Per day

The [Per day](/daily-rates-api/build/reference/per-day.md) reference describes every request and response field, with example values throughout:

* Temporal segments: lowercase `value`, `start`, and `end` fields, with an exclusive `end` date, so consecutive segments share their boundary date (see [Responses](/daily-rates-api/build/guidelines/responses.md)).
* Impersonation: which fields each token scope requires, and when a call returns a `403`.
* Per day covers daily prices, availability, and restrictions. For a taxes and fees breakdown, use the [Stay quotation](/quotation-api/build/reference/stay-quotation.md) endpoint.

**10 June 2026**

Reference update

## Promotion stay restrictions

Promotions in the response now expose `minStay` and `maxStay`: the minimum and maximum stay length, in nights, for the promotion to apply.

**1 May 2026**

Public release

## Initial public documentation

One Daily Rates API endpoint is publicly documented:

* **Per day**: full daily breakdown of availability, prices, and restrictions for one hotel over a date window.


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