> 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/rg-bridge-supply-push/interface-specifications-reservation-notification-service/points-to-remember.md).

# Points to remember

#### Message Communication and Handling

**REST Connectivity**:

* **Authentication**: Authentication is passed using basic authorization in REST connectivity.
  * If the credentials are found invalid, an error response needs to be returned.

**POS Source Element**:

* The `POS` source element contains `<CompanyName Code="BKNG"/>`, referring to the OTA/Channel code mapped in RateGain's Channel Manager system.
* For a complete list of OTA/Channel codes supported, please contact the RateGain team.

**Comments Handling**:

* Comments can be added either per room or globally for a reservation.
  * **Global Comments**: If any comment applies to the whole booking, it should be included in `ResGlobalInfo`.
  * **Room-specific Comments**: If a comment is required for a specific room, add it to the `RoomStay` section.

**Reservations Without Credit Card Details**:

* For reservations booked without credit card details, the `<Guarantee>` element may or may not be present in `ResGlobalInfo`.
  * If present, it should specify `GuaranteeCode` and `GuaranteeType` as follows:

\<Guarantee GuaranteeType="None" GuaranteeCode="NOT GUARANTEED"/>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.rategain.com/our-products/channel-manager/rg-bridge-supply-push/interface-specifications-reservation-notification-service/points-to-remember.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
