Skip to main content
Your system sends HTTP POST requests to a URL given by the D-EDGE team, authenticated with Basic Auth credentials issued by D-EDGE. The hosting model is described in the introduction.
Push bookings is the push half of the booking flow: as soon as a booking is confirmed, modified, or cancelled on your platform, your system sends it to the D-EDGE endpoint. It works together with Get bookings, and both are required. D-EDGE recognises a booking it already holds, so the two channels never duplicate.

The request you send

Send an HTTP POST with Content-Type: application/xml, the credentials in the Authorization header, and the XML as the raw body. Allow an HTTP timeout of up to 60 seconds. The body has the shape of a Get bookings response: a <message> opening with an empty <success/> element, then one booking message in a <bookings> element. The <success/> is required even though your call answers nothing. The examples follow one booking through its three actions, then show a booking carrying most optional elements of the booking message.

The response D-EDGE returns

The usual envelope: a <success>, a <failure>, or a <warning>. On an unexpected D-EDGE error, the body may be plain text rather than the XML envelope. Treat any response you cannot parse as XML like a 203 InternalError: keep the booking on your side, retry later, and contact us if it persists.
A <success> means the booking was read, not that it is integrated. Integration is asynchronous, and the definitive signal is the Confirm bookings message that follows. A booking pushed for an unknown hotel is refused with a <failure> (HotelNotLinked). A booking for an unknown room, or dated in the past, does not raise an error at push time. The other failures come from invalid XML, amounts that do not add up, or a processing error on the D-EDGE side, with the codes listed in Responses.

Retries

If you implement an automatic retry when no confirmation arrives, wait 15 minutes before pushing the same booking again. The push URL and its credentials are issued in the second certification phase and stay stable from then through production.