Skip to main content
D-EDGE sends an HTTP GET request to the URL you provide, authenticated with Basic Auth. The hosting model is described in the introduction.
Get hotel is how D-EDGE learns a hotel’s configuration on your platform: its room types, rates, and, when relevant, detailed occupancies. The response feeds the mapping stored on the D-EDGE side, and its priceModel attribute decides the shape of every future planning update. On the technical side, connecting a new hotel takes nothing more than your credentials and the hotel code; the steps are in Connect a new hotel. D-EDGE calls this interface when a hotel is connected, and again on request when its configuration changes. The retrieval is never triggered automatically: when you add, rename, or remove a room or rate, the hotel must ask D-EDGE to redo the mapping.

The request we send

string
required
The hotel identifier or code on your platform. Maximum 50 characters.
string
Requested language for room and rate names, as a 2-letter ISO code such as EN, FR, ES, or DE. When absent, English is expected, and English names are the only requirement.

The response we expect

Return 200 OK with Content-Type: application/xml and the structure below. On an error, return the failure envelope instead, still with 200 OK.
element
required
The root element.

Price models

The priceModel you return here is the most consequential attribute of the response: D-EDGE keeps it for the life of the connection and shapes every planning update from it. Decide it before you build the response, from how your platform stores prices, and keep the room attributes consistent with it: minOccupancy and maxOccupancy with PerPerson, plus the occupancies list with PerOccupancy. Changing it later means asking the hotel to have the mapping redone. The three models are compared on the Price models page.

Currency

Return the currency attribute in every response. It tells D-EDGE which currency your platform expects for the hotel, so every planning update reaches you in a currency you know in advance and can check. Without it, D-EDGE sends prices in the currency configured for the hotel on its side, and nothing tells you which one: a difference with your platform’s currency shows up only when the prices are wrong on your side. Declare the currency the hotel prices in on D-EDGE, one per hotel, and refuse any price reaching you in another currency with IncorrectPriceCurrency.

Update types

Declare an updateType other than PRI when a room and rate combination must not receive full updates. Tell the hotels you connect about the restriction, so their teams know why some updates do not reach your platform. Before using NoUpdate, discuss it with your D-EDGE Connectivity Project Manager: a combination with no inventory synchronisation at all is an overbooking risk.