Overview

Step 2 of 2 in the booking flow. Complete the booking by providing guest information and payment details. This confirms the reservation and creates the final booking.

When to Use

• After prebook - Call this after creating a prebook session
• Payment processing - Submit payment information to confirm booking
• Booking confirmation - Finalize the reservation

What You Get

• Booking ID - Unique identifier for the confirmed booking
• Hotel confirmation code - Reference code from the hotel
• Complete booking details - Dates, pricing, room information
• Cancellation policies - Terms for cancelling the booking
• Guest information - Confirmed guest details

Payment Methods

• ACC_CREDIT_CARD - Direct credit card payment. In sandbox mode, this can be used to simulate a booking without getting charged.
• TRANSACTION - Use when using Payment SDK (provide transactionId)
• CREDIT - Use account credit balance
• CREDIT_CARD - Credit card payment via secure endpoint. Accepts any credit or debit card, including virtual credit cards. Send card details via https://pci-book.liteapi.travel using the billingInfo object. Contact the team to enable this on your API key.

Testing

When testing sandbox bookings, simply use the ACC_CREDIT_CARD payment method. This allows you to simulate a booking without getting charged.

Required Information

• Prebook ID - From the prebook step
• Guest details - First name, last name, and email
• Payment information - Payment method and details

Quick Start

Provide the prebookId, guest information (firstName, lastName, email), and payment details. Returns confirmed booking with booking ID and confirmation code.

Vouchers

A voucher applied at prebook is checked again when you book, before anything is charged or booked. The booking is refused with HTTP 400, and nothing is charged, when since the prebook the voucher was deactivated or deleted (40033), its validity period no longer includes the booking time (40034), its discount was changed so that it no longer gives the amount applied at prebook, or its minimum spend was raised above the price (40035), its usage limit was reached by other bookings (40036), or its remaining budget no longer covers the amount applied at prebook (40037). The amount applied at prebook is never changed at book: prebook again to apply the voucher as it is now. The same clientReference can be used again.