Skip to main content
The Channel Manager API connects your distribution system to the D-EDGE Channel Manager. Through it, your platform receives the availability, prices, and restrictions of every hotel connected to you, within minutes of each change, and sends back the bookings made on your side. Exchanges are XML messages over HTTPS.

​
An API that runs on your endpoints

Most of this API lives on your side: you host the endpoints and D-EDGE calls them. Through these calls, D-EDGE reads your hotel configuration, pushes planning updates to you, pulls your bookings, and acknowledges each booking it integrates. Only one endpoint sits on the D-EDGE side, the one your system calls to push a booking the moment it is confirmed. Certification follows the same direction: D-EDGE tests your endpoints against test scenarios it publishes in advance.
Flow diagram: D-EDGE calls four endpoints hosted by the distribution system (get hotel, planning updates, get bookings, confirm bookings), and the distribution system calls one D-EDGE endpoint (push bookings)Flow diagram: D-EDGE calls four endpoints hosted by the distribution system (get hotel, planning updates, get bookings, confirm bookings), and the distribution system calls one D-EDGE endpoint (push bookings)
The Reference is therefore an interface specification: for each interface, it documents the request D-EDGE sends and the response your endpoint must return. Push bookings, the one interface D-EDGE hosts, reads the other way round.

​
The five interfaces

Get bookings and Push bookings are complementary, and both are required: the pull secures the flow, the push makes it immediate. D-EDGE recognises a booking it has already integrated, so the two channels never create duplicates.

​
What the API covers

  • Hotel configuration retrieval: room types, rates, and detailed occupancies, using your own codes.
  • Daily availability per room type, or per room type and rate.
  • Daily prices per room type and rate, and per occupancy when your price model calls for it, with optional meal plan detail.
  • Daily restrictions: minimum and maximum stay, closed to arrival, closed to departure, open or closed to sale.
  • Bookings, modifications, and cancellations, in both pull and push, with an integration acknowledgement.
Two things stay on your side by design: descriptive content (hotel, room, and rate descriptions) and cancellation policies. Your platform manages both.

​
Get started

Quick start

Build your first interface and answer a D-EDGE call.

Reference

Every interface: the request we send, the response we expect.

Guidelines

Credentials, message conventions, error handling, and price models.

Best practices

Price models, payment amounts, and a clean booking flow.