> For the complete documentation index, see [llms.txt](https://developer.siteminder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.siteminder.com/get-started/integration-types/booking-channel.md).
# Booking Channel
Access live hotel inventory and deliver reservations directly to properties through SiteMinder.
Your platform connects to SiteMinder to retrieve real-time availability, rates, and restrictions, then sends confirmed reservations back to the property.
> **API used:**
>
> [**SiteConnect**](/siteconnect-api/siteconnect-api.md) - direct connectivity with contracted properties.\
> [**Channels Plus**](/channels-plus-api/channels-plus-api.md) - access to properties and content without needing direct contracts.
{% hint style="warning" %}
**Each integration model operates independently.**
* Data retrieved through SiteConnect must be managed and returned through SiteConnect.
* Data retrieved through Channels Plus must be managed and returned through Channels Plus
* A property may use both models, but each operates as a separate integration.
{% endhint %}
***
### What you need to build with SiteConnect
{% hint style="success" %}
**Booking channels integrations using SiteConnect require a pilot property before going live.**
A single property is connected to production to validate that everything works correctly in a live environment before scaling to additional properties.
{% endhint %}
#### Core
Core functionality is required to go live and enables the essential data exchange required to go live.
* Rooms and Rates
* Availability
* Stop Sell
* Rates (OBP or PDP)
* Reservations
#### Additional
Additional functionality extends your integration beyond core certification scope. These are not required to go live but are recommended to deliver a complete booking channel integration.
* Other Restrictions (Min. Stay, Max. Stay, CTA and CTD)
* Modifications
* Cancellations
→ View the full [pmsXchange API Overview](/pmsxchange-api/guides/api-overview.md)
***
### What you need to build with Channels Plus
#### Core
Core functionality is required to go live and enables the essential data exchange required to go live.
* Get Properties and Property
* Lock, Confirm, Modify and Cancel Reservations
#### Additional
Additional functionality extends your integration beyond core certification scope.
* Get Reservation List
* Get Reservation Details
→ View the full [Channels Plus API Overview](/channels-plus-api/guides/api-overview.md)
{% hint style="success" icon="sparkles" %}
## Still have questions?
Use the :gitbook-assistant: **Ask** button at the top of the page to chat with our AI assistant — it can help you navigate the guide, understand requirements, and troubleshoot issues.
If you need more support, visit [Integration Support](/integration-support/integration-support.md).
{% endhint %}
---
# 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.siteminder.com/get-started/integration-types/booking-channel.md?ask=&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.