The extra prebook call performs any prebooking necessary for the extra and needs to be flexible enough to cover a range of extra types and supplements.
The booking token from the extra search results is needed in the prebook as it has a summary of the extra details that the API needs. The detailed structures of the prebook request and response calls are given below.
The structure of the XML will be:
The structure of the XML will be:
<ExtraPreBookRequest>
<LoginDetails>
<Login>TEST</Login>
<Password>TEST</Password>
</LoginDetails>
<BookingToken>{{BOOKINGTOKEN}}</BookingToken>
<DepartureDate>2022-08-19T00:00:00+01:00</DepartureDate>
<DepartureTime>12:00</DepartureTime>
<ReturnDate>2022-08-26T00:00:00+01:00</ReturnDate>
<ReturnTime>12:00</ReturnTime>
<GuestConfiguration>
<Adults>2</Adults>
</GuestConfiguration>
</ExtraPreBookRequest>
<ExtraPreBookResponse>
<ReturnStatus>
<Success>true</Success>
<Exceptions />
<ThirdPartyErrors />
</ReturnStatus>
<BookingToken>{{BOOKINGTOKEN}}</BookingToken>
<TotalPrice>69.00</TotalPrice>
<TotalCommission>6.870</TotalCommission>
<VATOnCommission>0.000</VATOnCommission>
<Cancellations>
<Cancellation>
<EndDate>2099-12-31T00:00:00</EndDate>
<StartDate>2022-06-10T00:00:00</StartDate>
<Amount>69.000</Amount>
</Cancellation>
</Cancellations>
<PaymentsDue>
<PaymentDue>
<Amount>62.13</Amount>
<DateDue>2022-06-10T00:00:00</DateDue>
</PaymentDue>
</PaymentsDue>
<CommissionType>Percentage</CommissionType>
<CommissionValue>10.00</CommissionValue>
<ExtraLocations />
<BondingID>0</BondingID>
<BookingQuestions />
<JoiningInstructions />
</ExtraPreBookResponse>