> ## 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. # Glossary > Hospitality terminology and D-EDGE concepts, decoded ## ADR Average Daily Rate. The mean nightly price across rooms over a date window. A core revenue-management metric, computed from a [Daily Rates](/daily-rates-api/get-started/introduction.md) response by averaging `totalPrice` across cells where the room is available. ## API key A single secret that authenticates every call to the [Gift Shop API](#gift-shop-api), sent as the `X-API-KEY` header. D-EDGE delivers it with the shop's configuration. The pricing and Booking Engine APIs use [OAuth 1.0](#oauth-1-0) instead, and the [CRM API](#crm-api) uses [OAuth 2.0](#oauth-2-0). ## Arrival date The first night of a guest's stay at a property. Distinct from the booking date, which is when the reservation was made. ## Availability Whether a room or rate is bookable on a given date. Driven by inventory levels, [restrictions](#restriction), and rate-management decisions. ## BAR Best Available Rate. The cheapest publicly available rate at a hotel for a given date and party. Distinct from member rates, private rates, or any rate restricted to a specific channel. ## Basket The set of rooms and extras a guest has added during a [Booking Engine API](#booking-engine-api) session, before they quote and confirm. Built up with the basket endpoints and reviewed in a single call before checkout. ## Beneficiary The person a [gift voucher](#gift-voucher) is issued to. When a [shopper](#shopper) buys a voucher for someone else, the beneficiary's name and email travel with the cart item, and D-EDGE emails them the voucher after payment. The shopper can also be their own beneficiary. ## Best Price API The D-EDGE service that returns the cheapest available offer at a hotel or across a group. Five public endpoints: [Calendar](/best-price-api/build/reference/calendar.md), [Rates](/best-price-api/build/reference/rates.md), [Rooms](/best-price-api/build/reference/rooms.md), [Hotels (Arrivals)](/best-price-api/build/reference/hotels-arrivals.md), and [Hotels (Stays)](/best-price-api/build/reference/hotels-stays.md). ## Booking engine Software running on a hotel's website that handles the booking funnel: date selection, room choice, guest details, payment. Booking engines often integrate Best Price to display live prices and availability before the visitor commits to a stay. ## Booking Engine API The D-EDGE service that powers a hotel's full direct booking funnel through a single stateful [session](#session): search, basket, quote, and confirmation, with descriptions, promotions, loyalty, and sales terms at each step. See the [Booking Engine API](/booking-engine-api/get-started/introduction.md). ## Booking funnel The sequence of steps a guest goes through to complete a reservation: date selection, room selection, guest details, payment, confirmation. [Booking engines](#booking-engine) own the funnel; the [Booking Engine API](#booking-engine-api) powers it end to end, while partner integrations can also pre-fill earlier steps using [Best Price](/best-price-api/get-started/introduction.md) or [Quotation](/quotation-api/get-started/introduction.md) data. ## Booking window The number of days between the date a reservation is made and the [arrival date](#arrival-date). The [CRM API](#crm-api) exposes it as the `bookingarrival` search field, which lets a query single out last-minute or long-lead bookings. ## Cancellation policy The conditions under which a booking can be cancelled or modified without penalty. Common types: flexible (free cancellation up to a deadline), partial refund, non-refundable. Every [rate plan](#rate-plan) carries its own cancellation policy, which often explains why two rates differ in price for the same room. The [Channel Manager API](#channel-manager-api) does not model cancellation policies: a [distributor](#distributor) manages them on its own platform and can pass the one applied to a booking as free text in the booking message. ## CDP Customer Data Platform. A system that assembles a unified profile per customer from every source that knows them. D-EDGE CRM Guest Profile is the CDP behind the [CRM API](#crm-api): it centralises what the platform, the [PMS](#pms), the guest, and the hotel staff each contribute to a [guest profile](#guest-profile). ## Certification The step of the [integration journey](/overview/get-started/your-integration-journey.md) where D-EDGE validates an integration before it connects real hotels, with scenarios that follow what the integration does. On the [Channel Manager API](#channel-manager-api), where D-EDGE calls the endpoints the distributor hosts, the scenarios are published in advance. See [Certification steps](/channel-manager-api/get-certified/certification-steps.md). ## Certification questionnaire The questionnaire a distributor completes before certification on the [Channel Manager API](#channel-manager-api). It describes how the platform stores availability, prices, and restrictions, and how it handles bookings; its answers decide which scenarios apply. See [Questionnaire](/channel-manager-api/get-certified/questionnaire.md). ## Channel manager Software that distributes a hotel's rates and inventory across multiple sales channels: [OTAs](#ota), GDS, metasearch, direct. D-EDGE partners with most major channel managers, and D-EDGE Channel Manager is its own: [distributors](#distributor) connect to it through the [Channel Manager API](#channel-manager-api). ## Channel Manager API The D-EDGE connectivity interface for [distributors](#distributor). XML over HTTPS, in five interfaces: four hosted on the distributor's side and called by D-EDGE (Get hotel, Planning updates, Get bookings, Confirm bookings), one hosted by D-EDGE (Push bookings). The distributor defines the credentials D-EDGE uses to call it. See the [Channel Manager API](/channel-manager-api/get-started/introduction.md). ## Criterion One condition of a [CRM API](#crm-api) search query, and the building block of a [segment](#segment): a field, an operator, and a value, all sent as strings. Which operators a field accepts depends on the field; the [Search criteria](/crm-api/build/guidelines/search-criteria.md) page lists every pair. ## CRM API The D-EDGE service that manages the [guest profiles](#guest-profile) of a hotel or [group](#group). Stateless: calls on guests and segments are scoped to an [entity](#entity), and every call is authenticated with an [OAuth 2.0](#oauth-2-0) bearer token. See the [CRM API](/crm-api/get-started/introduction.md). ## CRS Central Reservation System. The platform holding rate, availability, and inventory data for a hotel or hotel group. D-EDGE acts as a CRS for thousands of properties worldwide. ## Default occupancy The number of guests a [room type](#room-type)'s base price covers by default in D-EDGE, for instance 2 people for a double room. The hotel may also set prices for alternative occupancies, such as 1 person or 2 adults and 1 child. On the [Channel Manager API](#channel-manager-api) it is the occupancy behind `unitPrice` under `PerDay`, and the starting point from which D-EDGE derives the prices of the other [price models](#price-model). See [How D-EDGE picks each price](/channel-manager-api/build/guidelines/price-models.md#how-d-edge-picks-each-price). ## Direct booking A reservation made on the hotel's own channel (website, call centre, mobile app) rather than through a third-party [OTA](#ota). Direct bookings carry no distribution commission, which is why hoteliers actively work to grow this channel. ## Distributor A platform that sells hotel rooms it does not own: an [OTA](#ota), a [GDS](#gds), a wholesaler, a tour operator, or a marketplace. In the D-EDGE platform, a distributor receives the hotels' availability, prices, and restrictions and sends its bookings back, through a channel-manager connection such as the [Channel Manager API](#channel-manager-api). ## Engine ID The identifier of the booking engine configuration an integration runs against. D-EDGE issues it during onboarding, and you send it as `engineId` when you create a [Booking Engine API](#booking-engine-api) [session](#session). ## Entity The workspace that holds the [guest profiles](#guest-profile) a [CRM API](#crm-api) integration works on: a hotel or a [group](#group), identified by a UUID delivered with your credentials. Every CRM API route on a guest or a segment is scoped to an entity, and your token decides which entities you can read and write. ## Extra An add-on product a guest can attach to a booking, such as breakfast, parking, or a spa package. Added to the [basket](#basket) alongside rooms through the [Booking Engine API](#booking-engine-api). On the [Channel Manager API](#channel-manager-api), the extras a [distributor](#distributor) sells travel in the booking message, at room or booking level, each with a pricing type that sets how its total is computed. ## From price The "starting at" price displayed on a listing or hotel card to indicate the cheapest available offer over a date window (for example, "From €120 / night"). Best Price returns this price directly per room on [Rooms](/best-price-api/build/reference/rooms.md) and per hotel on [Hotels (Arrivals)](/best-price-api/build/reference/hotels-arrivals.md). On [Calendar](/best-price-api/build/reference/calendar.md), take the minimum price across the dates. Helps guests compare options at a glance before they commit to specific dates. ## GDS Global Distribution System. Network used by travel agents, corporate booking platforms, and tour operators to search and book travel inventory. Major networks: Amadeus, Sabre, Travelport. D-EDGE connects hotels to GDS networks for chain and corporate visibility. ## Gift Shop API The D-EDGE service that powers a hotel's online gift shop through a single stateful [session](#session): configuration, catalogue, cart with gift options, and a payment page hosted by D-EDGE. See the [Gift Shop API](/gift-shop-api/get-started/introduction.md). ## Gift voucher A prepaid product sold by a hotel's gift shop, delivered as a code the [beneficiary](#beneficiary) redeems later. Two kinds exist. A value voucher (`Direct`) is spent on the hotel's or group's [booking engine](#booking-engine), and always shows its value on the voucher document. A service voucher (`Indirect`), such as a spa session, is redeemed with the shop owner, at the hotel or within the group, which marks it as used; its price can be hidden. ## Group A hotel chain or multi-property entity managed under a single contract with D-EDGE. A group holds many [properties](#property). ## Guest configuration The composition of a [party](#party): number of adults, children (with ages), and infants. Every pricing request carries one in its `guests` field: a list of guest groups on Calendar, Hotels (Stays), Stay quotation, and Per day, a single group on Rates, Rooms, and Hotels (Arrivals). Check the reference page of the endpoint you call. ## Guest profile The record a hotel or [group](#group) holds about one guest in the D-EDGE CRM: identity, contact details, languages, stays, and the [segments](#segment) they belong to. Each attribute is a [sourced attribute](#sourced-attribute), so the profile keeps track of who contributed each piece of information. Managed through the [CRM API](#crm-api). ## Hotel Domain A D-EDGE feature that lets the booking engine run under the hotel's own domain name instead of the shared D-EDGE booking domain. The guest stays on the hotel's website throughout the [booking funnel](#booking-funnel), with one exception: the payment page is always hosted by D-EDGE. Built for the D-EDGE [booking engine](#booking-engine), it also benefits a [Booking Engine API](#booking-engine-api) integration, where the post-payment redirect points to the hotel's own URL so the confirmation page can live on the hotel's website. ## Initial synchronisation The stream of [planning updates](#planning-update) D-EDGE sends to a [distributor](#distributor) when a hotel is connected or its [mapping](#mapping) is redone: the hotel's full planning, up to two years ahead, usually split into one message per month. The distributor's endpoint must absorb it without refusing messages. See [Volume and timing](/channel-manager-api/build/guidelines/requests.md#volume-and-timing). ## Inventory The pool of bookable rooms available at a hotel for a given date. The number drops as bookings come in and is replenished by cancellations or rate-management decisions. ## Length of stay The number of nights of a reservation. Best Price responses surface minimum and maximum length-of-stay restrictions per arrival date. ## Loyalty programme A guest-rewards system where members earn points or unlock discounted rates by booking direct. Major chains run their own (Marriott Bonvoy, Hilton Honors, Accor ALL, IHG One Rewards). The Best Price API exposes [member rates](#member-rate) via the `loyaltyProgram.membershipLevel` filter. ## Mapping The correspondence D-EDGE stores between a hotel's rooms and rates in its own system and the codes a partner platform uses for them. On the [Channel Manager API](#channel-manager-api), D-EDGE builds it by reading the [distributor's](#distributor) configuration through Get hotel, then names the partner's codes in every message; the only D-EDGE identifier the partner sees is the booking reference on Confirm bookings. When rooms or rates change on the partner side, the hotel asks D-EDGE to redo the mapping. ## Master credentials On the [Channel Manager API](#channel-manager-api), one login and password a [distributor](#distributor) defines for all its hotels, as opposed to hotel-level credentials, one pair per hotel. D-EDGE presents them on every call to the distributor's endpoints. The only credential model that allows the all-hotels variant of Get bookings. See [Authentication](/channel-manager-api/build/guidelines/authentication.md). ## Meal plan The meals a [rate plan](#rate-plan) includes. On the [Channel Manager API](#channel-manager-api) a rate declares one of four types: `BreakfastIncluded`, `HalfBoard`, `FullBoard`, or `AllInclusive`. When the feature is enabled and the hotel prices meals apart from rooms, each [planning update](#planning-update) gives the price of one meal per adult and per child. That price is for information: the `unitPrice` of the update already holds the total room price, meals included. How D-EDGE adds the meals to the room price depends on the [price model](#price-model). See [Meal plans](/channel-manager-api/build/reference/planning-updates.md#meal-plans). ## Member rate A rate restricted to enrolled [loyalty programme](#loyalty-programme) members. Typically discounted from the public [BAR](#bar) by 5% to 15%, sometimes more for elite [tiers](#tier). The differentiator that justifies signing up. ## Mock environment A hosted endpoint that returns predefined, realistic but fictitious responses matching the shape of the live API. It needs no credentials and holds no real data, so you can explore endpoints and test an integration before you receive your access details. The [API collections](/overview/resources/api-collections.md) call a mock environment by default. ## Multi-hotel search A [Booking Engine API](#booking-engine-api) search run across every hotel in a [group](#group) rather than a single property. You open it by clearing `selectedHotelId` and adding a Localisation filter, which is how an integration offers nearby hotels when the chosen one is full. ## OAuth 1.0 The request-signing standard D-EDGE uses to authenticate calls to the pricing and Booking Engine APIs; the [Gift Shop API](#gift-shop-api) uses an [API key](#api-key) instead, and the [CRM API](#crm-api) uses [OAuth 2.0](#oauth-2-0). Each request carries an HMAC-SHA1 signature built from two credential pairs: a consumer key and secret that identify your integration, and a token key and secret that grant access to a hotel or [group](#group). See each API's Authentication page. ## OAuth 2.0 The token-based standard the [CRM API](#crm-api) uses. Your integration posts its client ID and client secret to a token endpoint (the client credentials flow) and sends the returned bearer token in the `Authorization` header of every call. Tokens are short-lived, so integrations cache and renew them. See the CRM API's [Authentication](/crm-api/build/guidelines/authentication.md) page. ## OTA Online Travel Agency. A third-party booking site such as Booking.com, Expedia, or Hotels.com. OTAs distribute hotel inventory in exchange for commission per booking. An OTA connects to D-EDGE hotels as a [distributor](#distributor), through the [Channel Manager API](#channel-manager-api). ## Party The hospitality-industry name for a group of guests booking together. Synonym for [guest configuration](#guest-configuration), the name the pricing APIs use for it. ## Per-night A pricing display where the headline number is the average price per night across the stay. Calendar and Hotels (Arrivals) return per-night-averaged prices when the minimum stay is greater than one. Check each endpoint's reference page for how its `totalPrice` is expressed. ## Pilot hotel A real hotel with live operational data, connected during the pilot step of the [integration journey](/overview/get-started/your-integration-journey.md) to validate an integration before wider rollout. Distinct from a [test hotel](#test-hotel), which carries no real data. ## Planning update A message the D-EDGE platform sends to a [distributor](#distributor) whenever a hotel's [availability](#availability), prices, or [restrictions](#restriction) change: a delta for one hotel, over any set of rooms, rates, and dates, in which an absent value means "unchanged". The main message of the [Channel Manager API](#channel-manager-api). ## PMS Property Management System. The on-property software that handles check-ins, room assignments, billing, housekeeping, and reporting. The PMS exchanges data with the [CRS](#crs) so rates, inventory, and reservations stay in sync. ## Price model How a [distributor's](#distributor) platform stores a hotel's prices, declared per hotel on the [Channel Manager API](#channel-manager-api) and applied to every [planning update](#planning-update). Three models exist: one price per room and day (`PerDay`), per person count (`PerPerson`), or per adult and child combination (`PerOccupancy`). See [Price models](/channel-manager-api/build/guidelines/price-models.md). ## Private rate A rate not visible on public channels. Restricted to specific corporate accounts, sales agents, or membership levels. On the [Booking Engine API](#booking-engine-api), a [promo code](#promo-code) seeded into the session can unlock one. ## Promo code A code a guest arrives with or enters that unlocks specific rates or offers. In a [Booking Engine API](#booking-engine-api) session it can be a rate code, an offer code, or a discount code, seeded into the session context; the session scope then reports which rates it grants. ## Promotion A discount applied to a rate for a specific date or condition. Best Price signals an active promotion through a separate field carrying the price before the discount. The [Booking Engine API](#booking-engine-api) returns the active public offer code for a session through its Promotion endpoint. ## Property Synonym for hotel in the hospitality industry. A single physical location with rooms, rates, and bookings. A [group](#group) holds many properties. ## Quote The price of a [basket](#basket) as returned by the [Booking Engine API](#booking-engine-api) before a guest accepts it and confirms. Re-quote right before confirmation, as prices and availability can change while the guest fills in their details. ## Rate plan A pricing scheme at a hotel. Common examples: Best Available Rate, Member Rate, Mobile Rate, Non-refundable, Corporate, Package. Each rate plan has its own conditions: [cancellation policy](#cancellation-policy), payment terms, breakfast inclusion, restrictions. ## Restriction A condition that limits when or how a rate can be booked. Common restrictions: minimum stay, maximum stay, no arrival, no departure, blackout dates. Best Price surfaces these in the response and lets you tune resolution via the request parameters. The [Channel Manager API](#channel-manager-api) pushes them to distributors in [planning updates](#planning-update). ## Revenue manager The person responsible for setting rates, deciding restrictions, and adjusting availability to maximise hotel revenue. Often the primary user of the [CRS](#crs), the [PMS](#pms), and the [RMS](#rms), and the audience of back-office tools like the [revenue manager dashboard](/daily-rates-api/resources/use-cases/revenue-manager-dashboard.md). ## RMS Revenue Management System. Software that recommends or automatically applies rate and inventory decisions to maximise hotel revenue. RMS providers ingest demand data, competitor rates, and historical performance, and write the resulting rates back to the [CRS](#crs). ## Room type A category of room at a hotel: Standard, Deluxe, Suite, Family, etc. Each room type has its own inventory pool, default capacity, and pricing within rate plans. ## Sales terms The terms and conditions a guest agrees to before completing a booking. The [Booking Engine API](#booking-engine-api) returns them per session, and a property can override the default text in its booking engine configuration. ## Segment A named group of [guest profiles](#guest-profile) within an [entity](#entity), defined by [criteria](#criterion) on the guests' attributes and stay history. The [CRM API](#crm-api) creates, reads, updates, and deletes them, lists the segments defined on an entity, and tells which segments a given guest belongs to. ## Sellable price The price a guest pays, commission included. Hotels set their prices that way in D-EDGE, so a sellable price is what the [Channel Manager API](#channel-manager-api) sends a [distributor](#distributor) by default. A net price follows the opposite convention: it is the amount the hotel keeps once the commission is deducted. If your platform works on net prices, raise it with D-EDGE rather than adapting the amounts yourself, and state what your booking amounts contain with `sellType` and the commission attributes. See [Fill the amounts for your payment model](/channel-manager-api/build/best-practices.md#fill-the-amounts-for-your-payment-model). ## Session The stateful context of a [Booking Engine API](#booking-engine-api) or [Gift Shop API](#gift-shop-api) integration. Creating a session returns a `sessionId` that you carry across every later call. For the Booking Engine API it holds the search context, filters, display options, and [basket](#basket); for the Gift Shop API it holds the culture and the cart. ## Shopper The person buying from a hotel's gift shop. The shopper pays for the cart and receives the purchase confirmation, while the voucher itself goes to the [beneficiary](#beneficiary) they designate. The shopper can be their own beneficiary. ## Sourced attribute The value shape of the [CRM API](#crm-api): a [guest profile](#guest-profile) attribute pairs its `value` with a `from` field naming who provided the information, `pms`, `guest`, `agent`, or `system`. Multi-valued attributes, such as emails and phones, are arrays of sourced values in which one entry can be marked as the preferred one. ## Task A background operation of the [CRM API](#crm-api). Merging guest profiles and computing a merge confidence answer straight away with a `location` header pointing at a task rather than with the result. Read the task until its `status` settles, then take the score or the merged profile's identifier from its `result`. ## Test hotel A fictitious hotel created for integration testing, used to build and test before connecting real properties. Distinct from a [pilot hotel](#pilot-hotel), which is a real hotel with live data. On the [Channel Manager API](#channel-manager-api), the test hotel lives on the [distributor's](#distributor) platform and D-EDGE connects to it; during certification, D-EDGE links its own test hotel to it. ## Tier A level within a [loyalty programme](#loyalty-programme). Typical pattern: basic, silver, gold, platinum. In the Best Price API, tiers are expressed numerically through the `loyaltyProgram.membershipLevel` parameter, following the numbering configured for the programme. Member rates often differ between tiers, with deeper discounts at higher levels. ## Update type What a room and rate combination can receive from D-EDGE on the [Channel Manager API](#channel-manager-api), declared per rate in Get hotel. Four values exist: prices, restrictions, and inventory (`PRI`, the default), inventory and restrictions only (`InvRest`), inventory only (`Inv`), or nothing (`NoUpdate`). It filters the [planning updates](#planning-update) D-EDGE sends for that combination. See [Update types](/channel-manager-api/build/reference/get-hotel.md#update-types). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.