> ## 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

> Manage a hotel's guest profiles, from creation to segmentation

The CRM API exposes D-EDGE CRM Guest Profile, the customer data platform (CDP) that centralises the guest data of a hotel or a group. Through it, you create and update guest profiles, and search and browse them and their bookings. You manage the segments they belong to, merge and unmerge duplicates, and honour a guest's privacy choices.

Calls on guests and segments are scoped to an **entity**, the workspace that holds the guest profiles you work on, and every call carries an OAuth bearer token. The API is stateless: there is no session to open or carry.

## Where your integration fits

A guest profile is built from four origins as the guest's journey unfolds. The booking arrives through the D-EDGE platform, the property management system sends the identity, the guest adds their own details after booking, and the hotel staff notes preferences during the stay. Your integration joins that flow through the CRM API: it reads everything the origins feed into the profile, and writes back what it learns on its side.

![Data-flow diagram: the D-EDGE platform, the property management system, the guest, and the hotel staff each feed a guest profile whose attributes carry their origin, and your integration reads and writes the profile through the CRM API](https://mintcdn.com/dedge/qh0OMArf4kAaSPdp/images/crm-data-flow-light.svg?fit=max\&auto=format\&n=qh0OMArf4kAaSPdp\&q=85\&s=0ee6974f454b9a60a32c8c00a807e82f)

Every attribute keeps its origin: a `from` field (`system`, `pms`, `guest`, or `agent`) sits next to each `value`, and your integration declares the real origin of the data it sends. Attributes that accept several values, such as emails, phones, and addresses, are lists in which one entry can be marked as `preferred`.

## Get started

> **[Quick start](/crm-api/get-started/quick-start.md)**
>
> Create your first guest profile in a few minutes.

> **[Reference](/crm-api/build/reference/guest/post-guests-create.md)**
>
> Every endpoint, grouped by capability.

> **[Guidelines](/crm-api/build/guidelines/authentication.md)**
>
> Authentication, request conventions, and response formats.

> **[Best practices](/crm-api/build/best-practices.md)**
>
> Patterns for clean profiles, from sourcing to deduplication.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.