> ## 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 Best Price API This changelog tracks public-facing changes to the Best Price API: new endpoints, breaking changes, deprecation notices, and behaviour adjustments worth knowing about. **9 October 2026** Reference ## Several restriction strategies in one call [Rates](/best-price-api/build/reference/rates.md), [Rooms](/best-price-api/build/reference/rooms.md), and [Hotels (Arrivals)](/best-price-api/build/reference/hotels-arrivals.md) accept a `behaviours` array: * With a single strategy, the response keeps its shape: one entry per rate, room, or hotel, with its best price over the period and the arrival date it applies to. * List one or more of `LowestLengthOfStay`, `CheapestStay`, and `EarliestAvailability`. Each rate, room, or hotel is then returned once per strategy, with the new `behaviour` response field telling you which one it was computed for. An empty list falls back to `behaviour`, then to `LowestLengthOfStay`. Send a single value in most cases, and list several only to replace separate calls: each extra strategy affects performance. * The single `behaviour` request property is deprecated on these three endpoints and can't be combined with a non-empty `behaviours`. Calendar keeps its single `behaviour`. * Rates and Rooms entries return `availability`: the number of rooms still available for the room and rate over the returned stay. * `filter.maximumStay` now accepts values from 1 to 31 on Calendar, Rates, Rooms, and Hotels (Arrivals). **1 September 2026** Reference ## Every field of the five endpoints The five [Reference](/best-price-api/build/reference/calendar.md) pages describe every request and response field, with example values throughout: * Impersonation: which fields each token scope requires, and when a call returns a `403`. * [Calendar](/best-price-api/build/reference/calendar.md) takes exactly one party in `guests`. The array is kept for forward compatibility, and a request with more than one party returns a `400`. **5 August 2026** New use case ## Multi-currency price display use case A new use case shows how to display prices in the guest's currency when the property sells in another one: one call in the property's currency, a public daily exchange rate feed, and a conversion at display time. See [Multi-currency price display](/best-price-api/resources/use-cases/multi-currency-price-display.md). **10 June 2026** Taxes and fees ## Taxes and fees on every endpoint All five Best Price endpoints now return four optional fields alongside each best price: `additionalTaxes` and `additionalFees` for amounts collected on top of `totalPrice` (at booking or on site), and `includedTaxes` and `includedFees` for amounts already part of `totalPrice`. **1 May 2026** Public release ## Initial public documentation Five Best Price endpoints are publicly documented: * **Calendar**: best price per arrival date for a single hotel. * **Rates**: best price per rate plan for a single hotel. * **Rooms**: best price per room type for a single hotel. * **Hotels (Arrivals)**: best price per hotel across multiple properties. * **Hotels (Stays)**: best price across hotels for a specific stay. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.