Skip to main content
This changelog tracks public-facing changes to the CRM API: new endpoints, breaking changes, deprecation notices, and behaviour adjustments worth knowing about.
​
Search criteria

​
Every search field and operator on one page

The new Search criteria page lists the fields a query can target, for guests and bookings, and the operators each one accepts. A date takes a YYYY-MM-DD value or a day keyword such as today. The same query model serves Search, Count, and Browse guests, Browse bookings, and the segments.
​
Six endpoints, two use cases

​
Full control over duplicates and segments

Six endpoints join the reference: score a set of profiles before you merge them, unmerge a guest, follow a background task, create and update a segment, and browse the bookings of an entity with their guests. Duplicate profile cleanup and Post-stay profile enrichment put them to work.
​
Public release

​
Initial public documentation

The CRM API joins the portal. It exposes D-EDGE CRM Guest Profile, the customer data platform that centralises a hotel’s or a group’s guest data:
  • Guest: create, read, update, and anonymise guest profiles built from sourced attributes.
  • Search: count, search, and browse guests with a shared query model.
  • Merge: merge duplicate profiles into one.
  • Segments: read the segments defined on an entity and the ones a guest belongs to, and delete a segment.