> ## 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. # Your integration journey > From first tests to a full rollout Every D-EDGE integration follows six steps, from your first tests against the mock environment to a full rollout. Each one sets clear expectations for D-EDGE and the partner, so the project stays on track. ## Journey at a glance ![The six steps of a D-EDGE integration, from exploring the APIs to scaling to more hotels](https://mintcdn.com/dedge/qh0OMArf4kAaSPdp/images/integration-journey-light.svg?fit=max\&auto=format\&n=qh0OMArf4kAaSPdp\&q=85\&s=4e4e926a5faae0dd968d8d1c4aefeddf) ## The six steps in detail ## 1. Explore and test the APIs Nothing to sign at this stage. The documentation is open to everyone, so your technical team can compare the APIs and pick the one that fits your scenario. Import the [API collections](/overview/resources/api-collections.md) and run requests against the [mock environment](/overview/resources/glossary.md#mock-environment): every endpoint answers with realistic data, and you need no credentials. ## 2. Share your project Once you know what you want to build, connect with the D-EDGE team to bring it to life. This step turns your tests into a real project. * **Discovery call**: you present your use case, the scope you have in mind, and the API you selected, and your technical team confirms it can build the connection. Request the call through the [partnership enquiry form](https://www.d-edge.com/partner-contact/). * **Partnership agreement**: the agreement between you and D-EDGE formalises the project, outlines any applicable project fees, and sets the foundation for everything that follows. It is also what opens access to production. ## 3. Build your integration You build the integration, and D-EDGE stays alongside you throughout. * **Kick-off call**: D-EDGE hosts a kick-off call to open the build. Reviewing the latest API version and preparing questions ahead of time helps make the session productive. * **Account creation**: D-EDGE creates a dedicated partner account with a [test hotel](/overview/resources/glossary.md#test-hotel), so you can build and test against fictitious data without impacting any real property. * **Credentials**: D-EDGE delivers the credentials needed to authenticate your API calls, along with the base URL of the environment you connect to. See the Authentication page of the API you are integrating with for the format and signing instructions. * **Development**: a dedicated D-EDGE Connectivity Project Manager works side by side with you throughout the build, providing support, guidance, and resources to meet D-EDGE standards. ## 4. Get certified Certification is the last checkpoint before your integration reaches real hotels. * **Preparation**: you complete a detailed questionnaire designed to spot potential bottlenecks before they impact your build. * **Planning**: you and D-EDGE plan the certification together: its scope, its duration, and the test cases, tailored to your implementation. * **Final interface submission**: your D-EDGE Connectivity Project Manager tests and validates your interface to confirm it handles real-world scenarios. On the Channel Manager API, the test cases are published in advance: see [Certification steps](/channel-manager-api/get-certified/certification-steps.md). ## 5. Go live with pilot hotels Once certified, the integration connects **3 to 5 [pilot hotels](/overview/resources/glossary.md#pilot-hotel)**. Pilot properties that already use D-EDGE onboard faster and are easier to troubleshoot. Setup time depends on the complexity of your integration. D-EDGE suggests a pilot duration based on averages from similar integrations, and you refine it together with your D-EDGE Connectivity Project Manager. ## 6. Scale to more hotels Once D-EDGE confirms the success of the pilot, your integration is cleared for rollout to more clients and properties. * **Project completion**: D-EDGE confirms the project is officially complete, agrees the contact points on each side, and asks for your feedback on the certification. * **New properties**: each property then joins through the process described in [Connect a new hotel](/overview/run-your-integration/connect-a-new-hotel.md). * **Ongoing support**: D-EDGE provides a standardised onboarding process and dedicated contacts to handle issues as the integration scales, listed on [Contact us](/overview/resources/contact-us.md). ## Ready to start your journey? When you are ready to move from tests to a project, complete our partnership enquiry form. The partnership team will review your request and respond within a few days. > **[Contact our partnership team](https://www.d-edge.com/partner-contact/)** > > Open the enquiry form. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.