Booking message

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4440" action="Create" currency="EUR"
         date="2027-04-14T10:03:25" totalAmount="397.00" paidAmount="397.00"
         dueAmount="0.00" payableAmount="397.00" origin="MySite.com"
         paxCount="3" adultCount="2" childCount="1" infantCount="0"
         commissionType="percent" commissionValue="10.00" sellType="gross"
         dayUse="false" arrivalTime="15:00Z" departureTime="11:00Z">
  <customer firstName="Alain" lastName="Dupont" title="Mr">
    <contact email="alain.dupont@example.com" phone="0620304050">
      <address city="Paris" country="FR" postalCode="75002">
        <![CDATA[24 rue du sentier]]>
      </address>
    </contact>
    <creditCard number="4111111111111111" cardHolder="Alain Dupont"
                expiryDate="2028-03" cardType="Visa" />
    <comment><![CDATA[Quiet room, please.]]></comment>
  </customer>
  <travelAgent name="My Travel Agency" id="IATA12456">
    <contact email="agency@example.com" phone="+33120304050" />
  </travelAgent>
  <distributor>
    <comment name="Cancel Policy">
      <![CDATA[In the event of a no-show, the first night is charged.]]>
    </comment>
    <comment name="Guaranty"><![CDATA[Credit card guarantee]]></comment>
  </distributor>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="62.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="63.00" rateCode="NR" />
        <stay date="2027-10-04" quantity="1" unitPrice="60.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Alain" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
    </room>
    <room id="SUP">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="70.50" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Helene" lastName="Dupont" title="Mrs" ageRange="10" />
        <guest firstName="Lea" lastName="Dupont" title="Miss"
               ageRange="8" birthDate="2019-02-05" />
      </guests>
    </room>
  </rooms>
</booking>

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4441" action="Create" currency="EUR"
         date="2027-09-14T10:03:25" totalAmount="249.00" paidAmount="0.00"
         dueAmount="249.00" payableAmount="0.00" origin="MySite.com"
         paxCount="1" adultCount="1" childCount="0" infantCount="0">
  <customer firstName="Jean" lastName="Dupont" title="Mr">
    <contact email="jean.dupont@example.com" />
  </customer>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="50.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Jean" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
      <extras>
        <extra from="2027-10-02" to="2027-10-04" quantity="1" unitPrice="16.00"
               extraCode="R894" extraName="Minibar" inclusive="false"
               pricingType="PerNight" />
        <extra from="2027-10-02" to="2027-10-04" quantity="2" unitPrice="8.50"
               extraCode="124TF" extraName="Breakfast" inclusive="false"
               pricingType="PerGuestPerNight" />
      </extras>
    </room>
  </rooms>
</booking>

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4440" action="Create" currency="EUR"
         date="2027-04-14T10:03:25" totalAmount="397.00" paidAmount="397.00"
         dueAmount="0.00" payableAmount="397.00" origin="MySite.com"
         paxCount="3" adultCount="2" childCount="1" infantCount="0"
         commissionType="percent" commissionValue="10.00" sellType="gross"
         dayUse="false" arrivalTime="15:00Z" departureTime="11:00Z">
  <customer firstName="Alain" lastName="Dupont" title="Mr">
    <contact email="alain.dupont@example.com" phone="0620304050">
      <address city="Paris" country="FR" postalCode="75002">
        <![CDATA[24 rue du sentier]]>
      </address>
    </contact>
    <creditCard number="4111111111111111" cardHolder="Alain Dupont"
                expiryDate="2028-03" cardType="Visa" />
    <comment><![CDATA[Quiet room, please.]]></comment>
  </customer>
  <travelAgent name="My Travel Agency" id="IATA12456">
    <contact email="agency@example.com" phone="+33120304050" />
  </travelAgent>
  <distributor>
    <comment name="Cancel Policy">
      <![CDATA[In the event of a no-show, the first night is charged.]]>
    </comment>
    <comment name="Guaranty"><![CDATA[Credit card guarantee]]></comment>
  </distributor>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="62.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="63.00" rateCode="NR" />
        <stay date="2027-10-04" quantity="1" unitPrice="60.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Alain" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
    </room>
    <room id="SUP">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="70.50" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Helene" lastName="Dupont" title="Mrs" ageRange="10" />
        <guest firstName="Lea" lastName="Dupont" title="Miss"
               ageRange="8" birthDate="2019-02-05" />
      </guests>
    </room>
  </rooms>
</booking>

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4441" action="Create" currency="EUR"
         date="2027-09-14T10:03:25" totalAmount="249.00" paidAmount="0.00"
         dueAmount="249.00" payableAmount="0.00" origin="MySite.com"
         paxCount="1" adultCount="1" childCount="0" infantCount="0">
  <customer firstName="Jean" lastName="Dupont" title="Mr">
    <contact email="jean.dupont@example.com" />
  </customer>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="50.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Jean" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
      <extras>
        <extra from="2027-10-02" to="2027-10-04" quantity="1" unitPrice="16.00"
               extraCode="R894" extraName="Minibar" inclusive="false"
               pricingType="PerNight" />
        <extra from="2027-10-02" to="2027-10-04" quantity="2" unitPrice="8.50"
               extraCode="124TF" extraName="Breakfast" inclusive="false"
               pricingType="PerGuestPerNight" />
      </extras>
    </room>
  </rooms>
</booking>

The <booking> element carries a reservation, a modification, or a cancellation from your platform to D-EDGE. The same structure serves both booking interfaces: it is what your endpoint returns inside <bookings> on Get bookings, and what your system sends on Push bookings. Three invariants keep a booking integrable, whatever the channel:

Amounts add up: totalAmount equals the sum of all nights (unitPrice × quantity) plus extras, taxes included.
Stay dates are constant: every room of a booking covers the same dates, and the stay is contiguous.
People are counted: one main customer with at least a first and last name (except on a cancellation), and one guest element per person in each room, each carrying an ageRange, named or not.

Structure

element

required

One booking.

Hide attributes

attribute · string

required

Your unique booking identifier, maximum 20 characters. The same id must be used again when the booking is modified or cancelled.

attribute · enum

required

What happened: Create, Modify, or Cancel.

attribute · string

required

The booking payment currency, 3-letter ISO code.

attribute · datetime

required

UTC date and time of the action: the creation, modification, or cancellation time, YYYY-MM-DDTHH:MM:SS.

attribute · decimal

required

Total booking amount, taxes included: the room or stay prices plus the extras. Positive, 2 decimal places.

attribute · decimal

required

Amount already paid by the customer, taxes included. Positive, 2 decimal places.

attribute · decimal

required

Amount the customer still pays on arrival, taxes included. Positive, 2 decimal places.

attribute · decimal

required

Amount the hotel charges back to you, the distributor, taxes included. Positive, 2 decimal places. How the four amounts combine per payment model is worked out in Best practices.

attribute · string

Origin of the booking: your platform or booking website name.

attribute · string

A finer origin, when your platform distinguishes one.

attribute · integer

required

Total number of people in the whole booking.

attribute · integer

Number of adults in the booking. Send adultCount, childCount, and infantCount together, or none of the three: with none, D-EDGE derives the split from the guest elements.

attribute · integer

Number of children. Sent together with adultCount and infantCount.

attribute · integer

Number of infants. Sent together with adultCount and childCount.

attribute · enum

How your commission is expressed, together with commissionValue: percent (a percentage of totalAmount) or amount (a fixed amount).

attribute · decimal

The percentage or the amount, depending on commissionType. Positive, 2 decimal places.

attribute · enum

Whether totalAmount is net (commission excluded, the hotel’s net revenue) or gross (commission included).

attribute · boolean

Marks a day-use booking, for information.

attribute · time

The customer’s arrival time, format HH:mmZ (the Z matters). Useful for day use, valid on any booking.

attribute · time

The customer’s departure time, same format.

Hide child elements

element

required

The main customer. firstName and lastName attributes are required except on a cancellation; title takes Mr, Mrs, or Miss (defaults to Mr). If your platform does not split first and last names, put everything in lastName.

Hide child elements

element · 0..1

The customer’s free-text comment, as text or CDATA.

element · 0..1

Contact details: email, phone, and fax attributes. The email is optional but strongly recommended when the customer provided a real one; never send a generic address.

Show child elements

element · 0..1

The postal address as text or CDATA, with postalCode, city, and country attributes (ISO 3166-1, 2 letters, upper case).

element · 0..1

The guarantee card, when your platform transmits it: number, cardHolder, expiryDate (YYYY-MM), cardType, and cardVerificationCode attributes. cardType takes Visa (the default when empty), AmericanExpress, MasterCard, JCB, or Dinner (Diners Club, spelled as the API expects it). The verification code is not required. Card details demand HTTPS end to end. If your platform cannot transmit them, make sure hotels can retrieve them on your side, and tell your D-EDGE Connectivity Project Manager: it changes how the connection is set up. What happens to the card once it reaches D-EDGE is described in Card data.

element · 0..1

The corporate company attached to the booking, stored as a company profile and passed on to provider systems such as PMSs. Required attributes: name and id (an identifier maintained on your side). Optional contact child with email and phone attributes and an address, as on the customer.

element · 0..1

The travel agency attached to the booking, same shape as company; the id commonly carries the IATA number, and the contact email is required.

element · 0..1

The booked rooms. Required except on a cancellation.

Hide child elements

element · 1..n

required

One booked room type, identified by its id attribute: your room code, as declared in Get hotel, maximum 50 characters. An unmapped code prevents the booking from being integrated.

Show child elements

element

required

The stay, day by day.

Show child elements

element · 1..n

required

One night: date (YYYY-MM-DD), quantity (rooms of this type that night), unitPrice (price of one room that night, 2 decimals), and rateCode (your rate code, maximum 50 characters; an unmapped value integrates the booking on an arbitrary rate).

element

required

The people staying in the room, one guest per person. D-EDGE counts them by ageRange to set the number of adults, children, and infants of the room, so send one element per person even when you know nothing about them.

Show child elements

element · 1..n

required

One person. ageRange is required: 10 adult, 8 child, 6 infant. Everything else is optional: firstName, lastName, title (one of Mr, Mrs, or Miss, no other value; Mr when absent), and birthDate (YYYY-MM-DD). An element carrying only an ageRange, such as <guest ageRange="8" />, is enough for the count; add the identity when your platform has it.

element · 0..1

Extras sold with this room. Same extra structure as the booking-level element below; the room level allows a per-room guest count in the price formulas.

element · 0..1

Extras sold at booking level, when they are not attached to a room.

Hide child elements

element · 1..n

required

One extra type. All attributes are required. When unitPrice, extraCode, quantity, inclusive, or pricingType is missing, the extra is dropped and the booking integrates without it, with an ExtraIntegrationError warning (codes 204 to 208 in Responses).

Show attributes

attribute · date

required

Start of the extra’s period, YYYY-MM-DD.

attribute · date

required

End of the period, included, YYYY-MM-DD.

attribute · string

required

The extra’s code on your platform, maximum 50 characters.

attribute · string

required

The extra’s name; keep it under 50 characters for readability.

attribute · integer

required

The quantity of this extra, without re-including guest or night counts: the formula does that.

attribute · decimal

required

The unit price, combined with pricingType to compute the total. See Extra price formulas below.

attribute · boolean

required

true when the extra is included or free (unitPrice is then 0), false when it is charged.

attribute · enum

required

How the total is computed: PerStay, PerNight, PerGuest, or PerGuestPerNight.

element · 0..1

Additional information from your platform, as comment children: as many as you need, each holding free text or CDATA, with an optional name attribute you choose. Cancel Policy and Guaranty below are examples, not a fixed list. This is where cancellation policies travel, since the API does not model them.

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4440" action="Create" currency="EUR"
         date="2027-04-14T10:03:25" totalAmount="397.00" paidAmount="397.00"
         dueAmount="0.00" payableAmount="397.00" origin="MySite.com"
         paxCount="3" adultCount="2" childCount="1" infantCount="0"
         commissionType="percent" commissionValue="10.00" sellType="gross"
         dayUse="false" arrivalTime="15:00Z" departureTime="11:00Z">
  <customer firstName="Alain" lastName="Dupont" title="Mr">
    <contact email="alain.dupont@example.com" phone="0620304050">
      <address city="Paris" country="FR" postalCode="75002">
        <![CDATA[24 rue du sentier]]>
      </address>
    </contact>
    <creditCard number="4111111111111111" cardHolder="Alain Dupont"
                expiryDate="2028-03" cardType="Visa" />
    <comment><![CDATA[Quiet room, please.]]></comment>
  </customer>
  <travelAgent name="My Travel Agency" id="IATA12456">
    <contact email="agency@example.com" phone="+33120304050" />
  </travelAgent>
  <distributor>
    <comment name="Cancel Policy">
      <![CDATA[In the event of a no-show, the first night is charged.]]>
    </comment>
    <comment name="Guaranty"><![CDATA[Credit card guarantee]]></comment>
  </distributor>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="62.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="63.00" rateCode="NR" />
        <stay date="2027-10-04" quantity="1" unitPrice="60.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Alain" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
    </room>
    <room id="SUP">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="70.50" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="70.50" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Helene" lastName="Dupont" title="Mrs" ageRange="10" />
        <guest firstName="Lea" lastName="Dupont" title="Miss"
               ageRange="8" birthDate="2019-02-05" />
      </guests>
    </room>
  </rooms>
</booking>

<?xml version="1.0" encoding="utf-8"?>
<booking id="EOC4441" action="Create" currency="EUR"
         date="2027-09-14T10:03:25" totalAmount="249.00" paidAmount="0.00"
         dueAmount="249.00" payableAmount="0.00" origin="MySite.com"
         paxCount="1" adultCount="1" childCount="0" infantCount="0">
  <customer firstName="Jean" lastName="Dupont" title="Mr">
    <contact email="jean.dupont@example.com" />
  </customer>
  <rooms>
    <room id="CLA">
      <stays>
        <stay date="2027-10-02" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-03" quantity="1" unitPrice="50.00" rateCode="BAR" />
        <stay date="2027-10-04" quantity="1" unitPrice="50.00" rateCode="BAR" />
      </stays>
      <guests>
        <guest firstName="Jean" lastName="Dupont" title="Mr" ageRange="10" />
      </guests>
      <extras>
        <extra from="2027-10-02" to="2027-10-04" quantity="1" unitPrice="16.00"
               extraCode="R894" extraName="Minibar" inclusive="false"
               pricingType="PerNight" />
        <extra from="2027-10-02" to="2027-10-04" quantity="2" unitPrice="8.50"
               extraCode="124TF" extraName="Breakfast" inclusive="false"
               pricingType="PerGuestPerNight" />
      </extras>
    </room>
  </rooms>
</booking>

Extra price formulas

The total price of an extra follows its pricingType, and the guest count in the formula depends on where the extra sits:

`pricingType`	Total price
`PerStay`	`unitPrice` × `quantity`
`PerNight`	`unitPrice` × `quantity` × number of nights (`from` to `to`)
`PerGuest`	`unitPrice` × `quantity` × guest count
`PerGuestPerNight`	`unitPrice` × `quantity` × guest count × number of nights

At room level, the guest count is the number of guest elements in the room. At booking level, it is the booking’s paxCount. In the room-level example above, the total checks out as 150 (three nights at 50) + 48 (minibar: 16 × 1 × 3 nights) + 51 (breakfast: 8.50 × 2 × 1 guest × 3 nights) = 249.00. Provide one extra element per extra type (extraCode), and remember the invariant: every extra amount counts towards totalAmount.

Card data

When your platform sends card details, D-EDGE routes the booking flow through its PCI environment before a booking reaches the rest of the platform. Tell your D-EDGE Connectivity Project Manager that your bookings carry cards. The routing is set up per connection, and D-EDGE raises a security alert when card numbers reach a connection without it. The routing covers the booking flow only:

The body of the requests you send on Push bookings.
The body of the responses you return on Get bookings.
Planning updates carry no card data and stay outside it.

Two things happen to a booking on the way in. The card number is replaced by a token, and the verification code is replaced by 000. Both replacements happen before the booking enters the D-EDGE platform, so the platform itself never holds the card. D-EDGE keeps the real card in its PCI vault, from which it is read or passed on to the right people and systems under strict rules. The detection runs over the whole message, not only creditCard. A card number or a verification code (CVV, CVC) found in any other element or attribute, such as a free-text comment, is treated as card data and replaced where it sits. The detection works on the shape of a value, so data that only looks like card data is replaced too. Keep these values out of every element other than creditCard:

A number of 12 to 19 digits that starts like a card number, such as 4 (Visa), 51–55 (Mastercard), or 34 and 37 (American Express).
A value that starts with CVV or CVC.

Send the card in creditCard all the same: it is where D-EDGE reads it. You never see a token. D-EDGE returns no booking to you on this API, so the replacements stay on the D-EDGE side of the flow.

Get started

Build

Get certified

Resources

Structure

Extra price formulas

Card data

​Structure

​Extra price formulas

​Card data

Structure

Extra price formulas

Card data