v1

latestOpenAPI 3.0.02026-07-247251950.2 KB
Make bookings

2. Complete a booking

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)
  • WALLET - Wallet payment method
  • CREDIT - Use account credit balance

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.

post/rates/book

Query parameters

timeoutinteger

Request body

prebookIdstring required

This identifier from the pre-booking step is used to confirm a booking rate

clientReferencestring

An optional client-defined reference ID acts as an idempotency key to prevent duplicate bookings. If a booking already exists with the same client reference, the API will return a 4005 error.

customTagsobject

Optional bag of up to 5 user-defined key/value labels persisted with the booking. Keys must match ^[A-Z0-9_-]+$ (uppercase letters, digits, -, _). Values are arbitrary strings up to 255 characters. These labels are returned on booking responses and can be used to filter the list endpoints via the customTags=KEY:VALUE,KEY2:VALUE2 query parameter.

Example request

{
  "customTags": {
    "SOURCE": "GOOGLE",
    "TIER": "GOLD"
  }
}

Response

Successful response

guestLevelinteger

The guest's loyalty or membership level, if applicable.

sandboxboolean

Indicates whether this booking is in a test/sandbox environment (true/false).