> ## 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. # Connect a new hotel > How a property joins an integration that is already live ![Properties connecting to a live integration, growing from a handful to many](https://mintcdn.com/dedge/qh0OMArf4kAaSPdp/images/connect-a-new-hotel-light.svg?fit=max\&auto=format\&n=qh0OMArf4kAaSPdp\&q=85\&s=9307ff6025d2d6b007089c67b09b545f) Once your integration is live and D-EDGE confirms the project is complete, every new property joins through the same process. It applies to each property individually, whatever the size of your portfolio. The steps depend on the API you integrate with: pick the tab of your API. **Most APIs** On the pricing, booking, and guest management APIs, D-EDGE opens the access and sends you what you need to call the API. ### 1. Hotel requests activation The property sends a written request to its D-EDGE account manager, asking D-EDGE to open API access for your integration. The request comes from the property, not from you: it owns the decision to share its data. ### 2. D-EDGE opens API access D-EDGE enables API access for that property. ### 3. D-EDGE sends the access details D-EDGE sends the access details for that property to the dedicated email address you provided during onboarding. What you receive depends on the API you integrate with: check the Authentication page of your API for the values it expects and how to use them. **Channel Manager API** On the Channel Manager API, the property and your platform both act before D-EDGE connects them. D-EDGE sends no planning update until the property has validated its mapping. ### 1. Hotel requests the connection The property selects your platform in the D-EDGE platform and requests the connection. The request comes from the property, not from you: it owns the decision to share its data. ### 2. You accept the request The request reaches you on your side. Accept it so that D-EDGE can start the setup. ### 3. D-EDGE creates the mapping D-EDGE calls your [Get hotel](/channel-manager-api/build/reference/get-hotel.md) endpoint with the hotel's code on your platform. It maps each room type and rate you return to the hotel's configuration in D-EDGE. ### 4. Hotel validates the mapping The property reviews the mapping in the D-EDGE platform and validates it. ### 5. D-EDGE starts the synchronisation Once the validation is in, D-EDGE sends the initial synchronisation: a stream of [planning updates](/channel-manager-api/build/reference/planning-updates.md) covering the hotel's full planning, up to two years ahead. ### 6. Hotel goes live From there, updates flow whenever something changes on the hotel's side, and bookings travel through [Get bookings](/channel-manager-api/build/reference/get-bookings.md) and [Push bookings](/channel-manager-api/build/reference/push-bookings.md). The property handles any later change to the mapping directly, such as a new room type or a new rate. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.