GET /getBookings?from=2027-04-20T20:00:00&to=2027-04-20T21:00:00&hotelId=1234 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
GET /getBookings?duration=1 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
<bookings hotelId="1234">
<booking id="EOCFGA" action="Create" currency="EUR"
date="2027-04-20T20:03:25" totalAmount="397.00"
paidAmount="0.00" dueAmount="397.00" payableAmount="0.00"
paxCount="2">
<customer firstName="Alain" lastName="Dupont">
<contact email="alain.dupont@example.com" />
</customer>
<rooms>
<room id="CLA">
<stays>
<stay date="2027-10-02" quantity="1" unitPrice="198.50" rateCode="BAR" />
<stay date="2027-10-03" quantity="1" unitPrice="198.50" rateCode="BAR" />
</stays>
<guests>
<guest firstName="Alain" lastName="Dupont" ageRange="10" />
<guest firstName="Marie" lastName="Dupont" title="Mrs" ageRange="10" />
</guests>
</room>
</rooms>
</booking>
<booking id="ELKJFHF" action="Cancel" currency="EUR"
date="2027-04-20T20:50:25" totalAmount="180.00"
paidAmount="0.00" dueAmount="180.00" payableAmount="0.00"
paxCount="1">
<customer />
</booking>
</bookings>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="3" message="BadAuthentication">
<comment><![CDATA[Credentials are invalid for this Hotel (1234)]]></comment>
</failure>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="203" message="InternalError">
<comment><![CDATA[duration (aaa) is not an integer]]></comment>
</failure>
</message>
Bookings
Get bookings
D-EDGE pulls new, modified, and cancelled bookings
GET /getBookings?from=2027-04-20T20:00:00&to=2027-04-20T21:00:00&hotelId=1234 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
GET /getBookings?duration=1 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
<bookings hotelId="1234">
<booking id="EOCFGA" action="Create" currency="EUR"
date="2027-04-20T20:03:25" totalAmount="397.00"
paidAmount="0.00" dueAmount="397.00" payableAmount="0.00"
paxCount="2">
<customer firstName="Alain" lastName="Dupont">
<contact email="alain.dupont@example.com" />
</customer>
<rooms>
<room id="CLA">
<stays>
<stay date="2027-10-02" quantity="1" unitPrice="198.50" rateCode="BAR" />
<stay date="2027-10-03" quantity="1" unitPrice="198.50" rateCode="BAR" />
</stays>
<guests>
<guest firstName="Alain" lastName="Dupont" ageRange="10" />
<guest firstName="Marie" lastName="Dupont" title="Mrs" ageRange="10" />
</guests>
</room>
</rooms>
</booking>
<booking id="ELKJFHF" action="Cancel" currency="EUR"
date="2027-04-20T20:50:25" totalAmount="180.00"
paidAmount="0.00" dueAmount="180.00" payableAmount="0.00"
paxCount="1">
<customer />
</booking>
</bookings>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="3" message="BadAuthentication">
<comment><![CDATA[Credentials are invalid for this Hotel (1234)]]></comment>
</failure>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="203" message="InternalError">
<comment><![CDATA[duration (aaa) is not an integer]]></comment>
</failure>
</message>
D-EDGE sends HTTP
GET requests to the URL you provide, authenticated with Basic Auth. The hosting model is described in the introduction.The request we send
Two variants exist. Your endpoint must implement the first; the second applies only when you provide master credentials:- Per hotel: the request carries a
hotelId. This variant is mandatory in all cases, and D-EDGE may query several hotels in parallel. - All connected hotels: no
hotelId, only possible when you provide master credentials.
from and to, or by duration. Both mechanisms are mandatory on your side; a given request uses one or the other, never both.
string
The hotel identifier or code on your platform, maximum 50 characters. Present on the per-hotel variant, absent on the all-hotels variant.
datetime
Start of the window, UTC,
YYYY-MM-DDTHH:MM:SS. Used together with to, exclusive with duration.datetime
End of the window, UTC, same format. Used together with
from, exclusive with duration.integer
Number of past hours to look back from the request time. Exclusive with
from and to.duration=1. When a parameter is malformed (a duration that is not an integer, a from or to that does not match the format), return a <failure> with code 203 (InternalError). Name the faulty parameter in the comment.
The two examples show one variant each: a one-hour window on one hotel, and the last hour on all hotels, which only master credentials allow.
GET /getBookings?from=2027-04-20T20:00:00&to=2027-04-20T21:00:00&hotelId=1234 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
GET /getBookings?duration=1 HTTP/1.1
Authorization: Basic dGVzdGhvdGVsOnRlc3RwYXNzd29yZA==
Accept: application/xml, text/xml
Host: yourdomain.com
What belongs in a window
A booking belongs to the window of its latest action: return it with theaction matching what happened last, dated with that action’s time. Take two bookings on 19 June: B1 created at 08:00, B2 created at 10:00 and cancelled at 10:30.
| Window requested | You return |
|---|---|
| 08:00 to 09:00 | B1 with action="Create" |
| 09:30 to 09:40 | Nothing |
| 09:50 to 10:10 | Nothing: B2’s status changed at 10:30, after this window |
| 10:20 to 11:00 | B2 with action="Cancel" |
The response we expect
Return200 OK with a <success> followed by the bookings, grouped in one <bookings> element per hotel. A quiet window returns the bare success. D-EDGE waits up to 30 seconds for this response, longer than the 5 seconds of the other interfaces, because a busy window can hold many bookings. On an error, return the failure envelope.
element
required
The root element.
Hide child elements
Hide child elements
element
required
Present on every successful response, even with no bookings.
element · 0..n
The bookings of one hotel, identified by its
hotelId attribute (your hotel code, maximum 50 characters). One element per hotel; absent when there is nothing to return.Hide child elements
Hide child elements
element · 1..n
required
One booking, with the structure documented on the Booking message page.
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
<bookings hotelId="1234">
<booking id="EOCFGA" action="Create" currency="EUR"
date="2027-04-20T20:03:25" totalAmount="397.00"
paidAmount="0.00" dueAmount="397.00" payableAmount="0.00"
paxCount="2">
<customer firstName="Alain" lastName="Dupont">
<contact email="alain.dupont@example.com" />
</customer>
<rooms>
<room id="CLA">
<stays>
<stay date="2027-10-02" quantity="1" unitPrice="198.50" rateCode="BAR" />
<stay date="2027-10-03" quantity="1" unitPrice="198.50" rateCode="BAR" />
</stays>
<guests>
<guest firstName="Alain" lastName="Dupont" ageRange="10" />
<guest firstName="Marie" lastName="Dupont" title="Mrs" ageRange="10" />
</guests>
</room>
</rooms>
</booking>
<booking id="ELKJFHF" action="Cancel" currency="EUR"
date="2027-04-20T20:50:25" totalAmount="180.00"
paidAmount="0.00" dueAmount="180.00" payableAmount="0.00"
paxCount="1">
<customer />
</booking>
</bookings>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<success />
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="3" message="BadAuthentication">
<comment><![CDATA[Credentials are invalid for this Hotel (1234)]]></comment>
</failure>
</message>
<?xml version="1.0" encoding="utf-8"?>
<message>
<failure type="203" message="InternalError">
<comment><![CDATA[duration (aaa) is not an integer]]></comment>
</failure>
</message>
<customer> are required: rooms, names, and contact details can be omitted. On a modification, resend the full booking under the same id with action="Modify".Was this page helpful?