> ## 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. # Introduction > Distribute D-EDGE hotel inventory on your platform and send bookings back The Channel Manager API connects your distribution system to the D-EDGE Channel Manager. Through it, your platform receives the availability, prices, and restrictions of every hotel connected to you, within minutes of each change, and sends back the bookings made on your side. Exchanges are XML messages over HTTPS. ## An API that runs on your endpoints Most of this API lives on your side: **you host the endpoints and D-EDGE calls them**. Through these calls, D-EDGE reads your hotel configuration, pushes planning updates to you, pulls your bookings, and acknowledges each booking it integrates. Only one endpoint sits on the D-EDGE side, the one your system calls to push a booking the moment it is confirmed. Certification follows the same direction: D-EDGE tests your endpoints against [test scenarios](/channel-manager-api/get-certified/test-scenarios.md) it publishes in advance. ![Flow diagram: D-EDGE calls four endpoints hosted by the distribution system (get hotel, planning updates, get bookings, confirm bookings), and the distribution system calls one D-EDGE endpoint (push bookings)](https://mintcdn.com/dedge/qh0OMArf4kAaSPdp/images/channel-manager-flow-light.svg?fit=max\&auto=format\&n=qh0OMArf4kAaSPdp\&q=85\&s=35fe1ab75ba4e19c0f18b5bb995171f3) The [Reference](/channel-manager-api/build/reference/get-hotel.md) is therefore an interface specification: for each interface, it documents the request D-EDGE sends and the response your endpoint must return. Push bookings, the one interface D-EDGE hosts, reads the other way round. ## The five interfaces | Interface | Hosted by | What it does | | - | - | - | | [Get hotel](/channel-manager-api/build/reference/get-hotel.md) | You | D-EDGE reads a hotel's rooms, rates, and occupancies to build the mapping | | [Planning updates](/channel-manager-api/build/reference/planning-updates.md) | You | D-EDGE pushes availability, prices, and restrictions whenever they change | | [Get bookings](/channel-manager-api/build/reference/get-bookings.md) | You | D-EDGE pulls the bookings created, modified, or cancelled on your platform | | [Push bookings](/channel-manager-api/build/reference/push-bookings.md) | D-EDGE | You send each booking in real time, as soon as it is confirmed | | [Confirm bookings](/channel-manager-api/build/reference/confirm-bookings.md) | You | D-EDGE acknowledges each booking it has integrated | Get bookings and Push bookings are complementary, and both are required: the pull secures the flow, the push makes it immediate. D-EDGE recognises a booking it has already integrated, so the two channels never create duplicates. ## What the API covers * Hotel configuration retrieval: room types, rates, and detailed occupancies, using your own codes. * Daily availability per room type, or per room type and rate. * Daily prices per room type and rate, and per occupancy when your price model calls for it, with optional [meal plan](/overview/resources/glossary.md#meal-plan) detail. * Daily restrictions: minimum and maximum stay, closed to arrival, closed to departure, open or closed to sale. * Bookings, modifications, and cancellations, in both pull and push, with an integration acknowledgement. Two things stay on your side by design: descriptive content (hotel, room, and rate descriptions) and cancellation policies. Your platform manages both. ## Get started > **[Quick start](/channel-manager-api/get-started/quick-start.md)** > > Build your first interface and answer a D-EDGE call. > **[Reference](/channel-manager-api/build/reference/get-hotel.md)** > > Every interface: the request we send, the response we expect. > **[Guidelines](/channel-manager-api/build/guidelines/authentication.md)** > > Credentials, message conventions, error handling, and price models. > **[Best practices](/channel-manager-api/build/best-practices.md)** > > Price models, payment amounts, and a clean booking flow. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.