> 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/channel-manager/direct-connect-demand-push/interface-specifications-reservation-notification-service/operation-reservation/faq.md).

# FAQ

**Reservation Guidelines and Testing**

**Reservation Creation**:

* Partners should always create 1 reservation per room booked.
  * If a guest books 2 units of a room, there should be 2 different `ReservationID`s created and notified to the DirectConnect Reservation service URL.

**Profile Details**:

* A reservation can be created using Individual Customer, Travel Agent, or Company profile details.
  * Refer to the sample XML zip file to understand how the `ProfileType` controls such bookings.
* **ResGuest Profile**:
  * Can be the Booker, the Guest, the Corporate, or the Company profile.
  * Several fields are relevant to one profile but not required for another.

**Additional Information**:

* **CVV**: Not supported for a reservation.
* **Tax Details**:
  * Only `AmountAfterTax` is needed if tax is included, with no separate tax details added to a reservation.
  * Only `AmountBeforeTax` is needed if tax is excluded from a reservation.
* **Comments**:
  * Can be placed in both `RoomStay` and `ResGlobalInfo` sections.
  * If comments are specific to a particular room, include them in the `RoomStay` section and not in `ResGlobalInfo`.

**Testing Reservation Scenarios**:

* Reservation scenarios can be tested using any REST Client tool like ARC or Postman.


---

# 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/channel-manager/direct-connect-demand-push/interface-specifications-reservation-notification-service/operation-reservation/faq.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.