> ## 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 > Sell a hotel's gift vouchers from catalogue to payment The Gift Shop API powers a hotel's online gift shop from end to end. Through a single session, you read the shop's configuration, browse its categories and products, build a guest's cart, and confirm it for payment, with gift-specific options such as a beneficiary, a personal message, and, on service vouchers, a hidden price. The Gift Shop API is **stateful**: you open a session, carry its identifier across calls, and the cart lives in that session until the guest pays. ## How the shop works A purchase runs as a connected sequence of steps: ### 1. Create a session Open a session for the gift shop owner: a hotel or a hotel group, with an optional culture. The API returns a `sessionId` that you carry on every later call and that holds the cart through the journey. ### 2. Read the configuration Pull the shop's details, theme, and accepted payment methods to render the storefront: name, address, contact, colours, logo, and fonts. ### 3. Browse the catalogue List the shop's categories and search its active products. Each product carries its description, pictures, price (fixed or a range), quantity limits, validity, and taxes. ### 4. Build the cart Add products to the guest's cart, with the gift options: send the voucher to the shopper or to a beneficiary, attach a personal message, and, on `Indirect` products, hide the price. Update or remove items as the guest changes their mind. ### 5. Confirm the cart Send the shopper's details to confirm the cart. The response returns a `redirectUrl` to the payment page. ### 6. Payment Once the guest is on that page, they enter their card and pay. Payment is hosted and handled by D-EDGE, so you never touch card details. ### 7. Retrieve the order After payment, read the order from the session: the voucher codes, their expiry dates, the shopper, and the payment summary. ## Two kinds of products Every product carries a `usage` field that says where the guest uses the voucher: * **`Direct`**: a value voucher. The beneficiary spends it on the hotel's or group's online D-EDGE booking engine: the code entered on the payment page deducts its value from the total. Its price always appears on the voucher document. * **`Indirect`**: a service, such as a spa treatment or a dinner. The beneficiary redeems the voucher with the shop owner, at the hotel or within the group, which marks it as used in the D-EDGE platform. Its price can be hidden with `hidePrice`. The field travels with each voucher through the cart and the order, so your interface can tell the guest where each purchase can be used. ## Get started > **[Quick start](/gift-shop-api/get-started/quick-start.md)** > > Create your first session and run your first call in a few minutes. > **[Reference](/gift-shop-api/build/reference/session/post-session.md)** > > Every endpoint, grouped by stage of the journey. > **[Guidelines](/gift-shop-api/build/guidelines/authentication.md)** > > Authentication, request conventions, and response formats. > **[Best practices](/gift-shop-api/build/best-practices.md)** > > Patterns to run the shop reliably, from caching to session recovery. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.