canonical: https://jentic.com/apis/channelrush.com/channelrush

# ChannelRUSH Channel Manager API

ChannelRUSH is a hotel channel manager that synchronises rates, availability, and reservations across online travel agencies and direct booking channels. The API exposes the property model end-to-end: properties, rooms, per-day availability, rate plans, and inbound reservations, all addressable by property ID. It is intended for property management systems, revenue managers, and integrators that need a single point of control for distribution across multiple OTA channels.

## For AI agents

Manage hotel properties, rooms, per-date availability, rate plans, and OTA-sourced reservations through a single channel manager API. Useful for revenue management bots and property management system integrations.

## Scope

Does not handle direct payment processing, guest CRM, front-desk operations, or housekeeping management - use for hotel rate, availability, and reservation distribution only.

## Capabilities

- Create and update hotel properties with the /properties endpoints, including address and metadata
- Define and edit room types within a property via `/properties/{propertyId}/rooms`
- Push per-date availability counts to all connected channels through PUT `/properties/{propertyId}/availability`
- Update rate plans and nightly prices for any room type with PUT `/properties/{propertyId}/rates`
- Pull inbound reservations aggregated from connected OTAs via /reservations and `/reservations/{reservationId}`
- Read current availability and rates back from the channel manager to reconcile against the property's PMS

## Use cases

### Distribute Availability to OTAs

Hotels and property management systems push nightly availability counts and stop-sell flags through PUT `/properties/{propertyId}/availability` so that Booking.com, Expedia, and other connected OTAs see a single source of truth. The channel manager fans the update out to each channel, eliminating the need for the PMS to integrate with each OTA directly.

Example prompt: Update PUT `/properties/{propertyId}/availability` with 5 rooms available for 2026-07-15 and confirm the response succeeded

### Dynamic Rate Updates

Revenue management systems and pricing bots adjust nightly rates in response to occupancy, lead time, and demand signals. PUT `/properties/{propertyId}/rates` accepts a rate plan and price by date or stay range, and ChannelRUSH propagates the change to every connected OTA. This is critical for hotels that change prices multiple times per day.

Example prompt: Set PUT `/properties/{propertyId}/rates` for the standard double room to 189 GBP per night for 2026-07-12 to 2026-07-14

### Centralized Reservation Pull

Property management systems poll /reservations on a schedule to pull in new bookings from every connected OTA without integrating with each one separately. Reservation IDs can be looked up individually with `/reservations/{reservationId}` for full guest, room, and rate detail before posting into the PMS.

Example prompt: Call GET /reservations filtered to the last 24 hours and import each new booking ID into the PMS

### Agent-Driven Hotel Operations via Jentic

An AI agent with an instruction like 'mark the deluxe king as sold out next Friday across all channels' can resolve the operation through Jentic. It searches for the availability update operation, looks up the relevant property and room IDs, and executes the PUT call with a zero count for the target date - without ever holding the API key.

Example prompt: Search Jentic for 'update hotel availability', resolve the property and room IDs, and PUT a zero-count update for the target date

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/properties` | List managed properties |
| POST | `/properties` | Add a new property to the channel manager |
| GET | `/properties/{propertyId}/rooms` | List room types for a property |
| PUT | `/properties/{propertyId}/availability` | Push per-date availability to all channels |
| PUT | `/properties/{propertyId}/rates` | Update rate plans and nightly prices |
| GET | `/reservations` | List reservations aggregated across OTA channels |
| GET | `/reservations/{reservationId}` | Retrieve a single reservation by ID |

## Key resources

- **Properties** — Hotel-level records with address, contact, and metadata for each managed property
- **Rooms** — Room types configured under each property, used as the unit for availability and rate updates
- **Availability** — Per-date counts of bookable units pushed out to all connected OTA channels
- **Rates** — Rate plans and nightly prices propagated to every connected channel
- **Reservations** — Inbound bookings aggregated from connected OTAs in a single feed

## Why Jentic

- **Setup:** Wiring ChannelRUSH by hand means learning its X-API-Key header auth and attaching the key to every property, rate, and reservation call yourself. Through Jentic you install once, import ChannelRUSH from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ChannelRUSH puts the property id in the URL path (`/properties/{propertyId}/...`), so a rule can pin your agent to one property: it can update availability and rates for that property and nothing else. You choose the operations it may call, so property creation is not included unless you add it.
- **Credential handling:** Your ChannelRUSH API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'update hotel availability across channels' or 'pull new OTA reservations', and Jentic returns the matching ChannelRUSH operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudbeds API** — Cloudbeds offers an integrated PMS plus channel manager; ChannelRUSH focuses purely on channel management.
- **BookingSync API** — BookingSync is a vacation-rental-focused channel manager; ChannelRUSH targets hotel distribution.
- **Booking.com API** — Booking.com is a downstream OTA channel; ChannelRUSH distributes rates and availability into it.

## FAQ

### What authentication does the ChannelRUSH API use?

ChannelRUSH uses an API key passed in the X-API-Key header on every request. Through Jentic, the key stays in your Jentic One instance and the agent receives a scoped execution token rather than the raw secret.

### Can I update rates for multiple OTA channels at once with the ChannelRUSH API?

Yes. PUT `/properties/{propertyId}/rates` is a single call that ChannelRUSH then fans out to every connected channel. You do not call each OTA separately; the channel manager handles the distribution.

### How do I push availability for a specific date with the ChannelRUSH API?

Send PUT `/properties/{propertyId}/availability` with a payload that includes the room ID, date, and bookable count. Use a count of zero to stop-sell. The change propagates to all linked OTAs.

### What are the rate limits for the ChannelRUSH API?

ChannelRUSH does not publish a fixed public rate limit. As a hotel-distribution API, batched availability and rate updates are preferred over high-frequency individual calls; back off on HTTP 429 responses.

### How do I pull new reservations through Jentic?

Install jentic with pip install jentic, search for 'list hotel reservations', load the schema for GET /reservations, and execute. Run Jentic One, the self-hosted execution layer, to issue an agent API key.

### Does the ChannelRUSH API support modifying existing reservations?

The current public endpoints support reading reservations via GET /reservations and GET `/reservations/{reservationId}.` Modification flows are typically initiated by the originating OTA and synced back; check ChannelRUSH support for specific cancel or modify endpoints.

### Can I limit what my agent is allowed to do with the ChannelRUSH Channel Manager API?

Yes. Because ChannelRUSH puts the property ID in the URL path (`/properties/{propertyId}/...`), your rules in your own self-hosted Jentic One instance can pin the agent to a single property so it can push availability and update rates for that property and nothing else. You decide which operations the agent may call, so it can be allowed to run PUT `/properties/{propertyId}/availability` and PUT `/properties/{propertyId}/rates` while property creation via POST /properties stays off unless you add it. The stored API key is injected only at execution time, so the agent scopes what it does without ever holding the raw credential.