Last updated

Request to Book (RtB) API

Request to Book is a new booking model that offers eligible partners full control over the booking flow. Unlike the Instant Booking model, where guests can book a property directly, Request to Book requires guests to send a booking request that the partner can accept or decline.

The goal of RtB is to provide partners with an additional level of trust and reassurance when welcoming guests into their home.

Using our Request to Book API, you can enable eligible home properties to work with on the Request to Book model.

RtB flow

Provided the property is eligible and enabled to receive booking requests, these are the steps that the guest and the partner should take before an RtB reservation is confirmed:

  1. The guest sends a booking request to a partner’s property at least three days before the check-in date. (Please note that RtB properties are excluded from search results with check-in dates less than 3 days.)
  2. Partner receives a booking request notification and has 24 hours to accept or decline. If the partner does not accept or reject the booking request in time, the booking request will expire.
  3. If the partner accepts the request, the guest has 24 hours to complete their booking and confirm their stay. If the guest does not complete the booking in time, the booking request will expire and no reservation will be made.

Request to Book flow diagram

Key takeaways

Here are the key takeaways for working with Request to Book model using RtB API on

  1. Only for eligible properties – RtB is a new booking model only avilabile for eligible properties.
  2. Content API to opt-in & opt-out of RtB – Content API allows you to create and modify properties on We are leveraging this API to opt-in & opt-out eligible properties to the RtB model. Head to our onboarding article for more details on opting-in & opting-out of RtB.
  3. RtB API to manage booking requests – RtB API is designed to provide Request to Book (RtB) functionality to connected partners.
  4. RtB property visibility – Guests can only see Request to Book properties if they’re searching for stays with a check-in date more than three days away. If a guest wants to make a last-minute booking, they can only book an Instant Booking property.
  5. No pre-reservation messaging – Partners cannot communicate directly with the guest until the RtB reservation is confirmed by the guest. Messaging is – as of now – only available for confirmed reservations, post-booking via Messaging API or Extranet.
  6. Availability is not blocked, price can change – We are not blocking the availability for booking requests, therefore the price is subject to change. Which means it's possible that the price is higher or lower by the time partner approves and the guest confirms. Guest will be notified of this change and can decide to continue with the changed price or not.
  7. RtB ID ≠ Reservation ID – A reservationId is not the same as the bookingRequestId. A reservation – as in a regular Booking reservation – is created when the guest finalises their booking after receiving the approval from the property. This moves the booking request to Booked state – which is when the resulting reservationId is added to the BookingRequest object (head to object schema for more information).

For more information, see the FAQs section of the Request To Book article in Partner Hub.

Getting started

Dive into our technical documentation to get started!