> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/our-products/smart-distribution/book-and-cancel-reservation/book-api.md).

# Book API

### Overview <a href="#bookapi-overview" id="bookapi-overview"></a>

UltraDirect supports session control for all booking transactions. This means the hotel CRS (Central Reservation System) will temporarily hold booking, modification, and cancellation requests until a subsequent request to complete or ignore the action is received and processed.

Affiliate partners (demand partners integrating with RateGain) can choose between **active** or **passive** participation in session control:

1. **Active Participation**:
   * The affiliate sends two messages per transaction: one to initiate the booking, modification, or cancellation and another to complete (commit) or ignore the transaction.
   * A transaction is only finalized when it is committed. Consequently, the confirmation number or cancellation number is returned only in response to a commit transaction.
2. **Passive Participation**:
   * RateGain automatically sends the commit or ignore message to the CRS on behalf of the affiliate.
   * The affiliate sends only one request message per transaction and receives the confirmation or cancellation number directly in the response.

**Note**:\
This document focuses exclusively on the **passive mode** of session control. In the case of RateGain Pull connectivity, RateGain handles the commit or ignore message to the CRS on behalf of the affiliate. Therefore, affiliates only need to send a single request message per transaction to receive the confirmation or cancellation number.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.rategain.com/our-products/smart-distribution/book-and-cancel-reservation/book-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.