Skip to main content
Contact
Login
Login
Contact

Hotel Channel Manager API for PMS

An API for your systems. A back office for your teams.

For PMS companies that build distribution into their product, and for hotel groups whose own systems run the portfolio. Your system sends rates and availability once, in JSON or OpenTravel XML. Every channel gets them, and your team sees every update, booking and property in one back office.

Discuss your integrationBrowse the API reference
The ChannelRUSH Rates and Availability grid for a demo beach resort: two weeks of availability, rates and two-night minimum stays on the ChannelRUSH CRS channel.
JSON · RequestPOST /api/v2/ariupdate
{
  "propertyId": "2177",
  "items": [{
    "roomTypeId": "OVK",
    "ratePlanId": "STD",
    "dateRange": {
      "startDate": "2026-10-19",
      "endDate": "2026-10-23"
    },
    "sellRate": 259.00,
    "currencyCode": "USD",
    "allocation": 15,
    "minNights": 2
  }]
}
Request fields from the JSON v2 schema. The values are the ones in the screenshot.

The rate your system sent, live in the back office.

Build the integration once. Reach every channel.

  • 200+ channels: OTAs, wholesalers, GDS and metasearch
  • 50+ PMS integrations already running on it
  • $0 certification or setup fees per channel
  • JSON or XML REST JSON v2, or OpenTravel 2007B over HTNG 1.1
  • Booking.com
  • Expedia
  • Agoda
  • Ctrip
  • HotelTonight
  • HotelBeds
  • Hotels.com
  • Sabre

The back office behind the API

API-only providers give you an endpoint and a support inbox. With ChannelRUSH your team also gets the back office your hotels' distribution runs on: every property, every update, every booking. These are real screens from our demo portfolio.

The ChannelRUSH Accounts screen listing the demo organization's properties with each one's PMS and channel connections, and the property switcher open.

One login across the portfolio

Every hotel you onboard or operate sits in one account, grouped by organization, with each property's PMS and channel connections listed. Pick a property from the switcher and you are working on it, on the hotel's behalf, without a separate login.

  1. A searchable property switcher on every screen.
  2. Organizations and their properties in one account: your own hotels and every hotel you manage.
  3. Each property's connections: its PMS, its OTAs, the CRS and the booking engine.
Get a back-office walkthrough

How the API and the back office fit together

Your system stays the source of truth. ChannelRUSH does the distribution, and the back office shows all of it to your team.

  1. Your systemsPMS, RMS, data warehouse, internal tools
  2. Channel Manager APIJSON v2: /api/v2/*OTA 2007B, HTNG 1.1: /channels/v2/*
  3. ChannelRUSHMappings, rate rules, restrictions, delivery
  4. 200+ channelsOTAs, wholesalers, GDS, metasearch, your booking engine

Rates, availability, restrictions

Reservations, by push or poll

The back office: every property, update, booking and log, for your team

A PMS partner account

  • Harborline Inn Newport
  • Harborline Inn Mystic
  • Harborline Inn Bar Harbor
Each hotel you onboard sits under it. Your support team opens any of them, with no separate login.

  • Real-time ARI

    Rates, availability and restrictions go to every connected channel as soon as your system sends them. Name specific channels with ChannelIds when only some should change.

  • Push or poll

    New, modified and cancelled reservations come back by push to your endpoint, or you poll for them on your own schedule.

  • One back office

    Everything the API does is visible to your team, per property and across the portfolio, with the raw messages behind it.

One API, two kinds of portfolio

PMS companies and hotel groups build on the same API and get the same back office. What differs is whose hotels they are.

For PMS companies

Channel distribution you embed into your product

Build the integration once, and every hotel you bring on can sell on every channel we connect. Your product, UI and brand stay in front, Powered by ChannelRUSH underneath. Your hotels manage distribution inside the PMS they already use, and you keep the customer relationship.

With an API-only provider
A support ticket every time a hotel asks why a rate never reached Booking.com.
With ChannelRUSH
Your support team opens the hotel, sees what your system sent and what went out, and fixes the mapping themselves.
  • Every hotel you onboard, under your partner account
  • Work on any hotel's behalf without its login
  • Alerts when a hotel's PMS feed goes quiet
How PMS partnerships work

For hotel groups and management companies

Your systems drive the whole portfolio

Connect your in-house PMS, RMS, data warehouse or internal tools once, and run distribution for every property from them. Your teams work in one back office across the group, with portfolio reports and templates that push one configuration to many hotels.

With an API-only provider
Twelve hotels, twelve extranets, and nobody can say which one is wrong.
With ChannelRUSH
One back office for the group: per-channel status for every property, and Org Templates to change them all at once.
  • Portfolio reports across every property
  • Org Templates: one configuration, many properties
  • Logins for regional and on-site staff, limited to their hotels
How ChannelRUSH works for hotel groups

Two spec formats. Your call.

The JSON v2 API reads settings with POST /api/v2/settings and sends ARI updates with POST /api/v2/ariupdate. OpenTravel-compliant XML is also available; see the full XML specification below for its SOAP messages and provider credentials.

Both are fully documented. Both hit the same production infrastructure.

JSON v2 endpoints

Settings

GET/api/v2/channels
The channels connected to your properties
GET/api/v2/connectioncheck
Check your credentials and connection
POST/api/v2/settings
Room types and rate plans for a property

Rates and availability

POST/api/v2/ari
Read the rates and availability we hold
POST/api/v2/ariupdate
Send rates, availability and restrictions

Reservations

POST/api/v2/book
Create a booking
POST/api/v2/res
Pick up new, modified and cancelled reservations
POST/api/v2/resconfirm
Confirm the reservations you picked up
POST/api/v2/reservations
Retrieve existing reservations
JSON · RequestPOST /api/v2/settings
Authorization: Bearer <JWT>
Content-Type: application/json

{
  "propertyId": "ABC123"
}
JSON · Error responseHTTP 200
{
  "settings": null,
  "messages": [
    {
      "code": "-1",
      "message": "Settings not configured or enabled.",
      "messageType": "Error"
    }
  ],
  "successful": false
}

JSON v2 settings example: request built from the published schema; error response reproduced from its documented example. HTTP 200 alone does not mean success—check successful and messages.

View JSON v2 OpenAPI specification

Connecting more than distribution?

Explore the CRS API if your integration also needs central reservation workflows or a custom direct-booking experience.

Day one: a sandbox in your inbox

When we set up your sandbox, one email brings everything you need to send a first request: a back-office login, endpoints, credentials and a test property with its room and rate IDs.

  1. Your own back office

    A login to the test back office, so you can watch each message you send arrive and go out.

  2. Endpoints and credentials

    The Swagger documentation, the test server and your provider login, including the Authorization header.

  3. A test property

    Room type and rate plan IDs to map against, ready to take ARI and send reservations.

  4. Your first request

    A ready-made POST /api/v2/settings call and the response to expect.

From ChannelRUSH Support <support@channelrush.com>

Subject ChannelRUSH API Test Account Info - Your Company

Greetings,

Your ChannelRUSH PMS API Test Account is now active and ready for development.

ChannelRUSH Extranet Login Info

https://test.channelrush.net
u: you@yourcompany.example
p: ••••••••
o: ••••

Documentation - Swagger

https://testcm.channelrush.net/index.html

https://testcm.channelrush.net/api/v2/ariupdate

U: ••••••••
P: ••••••••
Authorization: Bearer ••••••••

Test Property Configuration

Room Types         Rate Plans
SGL - Single       BAR - BAR
DBL - Double       NRF - NRF
TRP - Triple
SUI - Suite

Next Steps

POST https://testcm.channelrush.net/api/v2/settings
{
  "PropertyId": "••••"
}

EXPECTED RESPONSE
{ "settings": { … }, "messages": [], "successful": true }
The welcome email our team sends with every sandbox, with logins and credentials masked.
ChannelRUSH Onboarding

Getting Started — Next Steps

01

Share your integration scope

Tell us about your PMS or platform, integration scope, and the channels you need to reach using the integration enquiry form below.

02

Technical Call

We walk your team through the JSON v2 or XML specification, its authentication model, and webhook/poll setup. Typical integration timeline runs 2–4 weeks for most partners.

03

Sandbox Account

Sandbox credentials typically within 24 hours of the call. Build against real endpoints — no toy environment.

Ready for a sandbox?

Request your sandbox

For PMS companies and hotel groups

Let’s discuss your integration.

Tell us what you run and what you want to connect, whether that is a PMS with hundreds of hotels or a group's in-house stack. We will come back with the next steps and a time for a technical call.

/ FAQ /

Frequently Asked Questions

The JSON v2 API uses the Authorization header with Bearer followed by a JWT. The XML API uses SOAP HTNG v1.1 provider credentials. See the API documentation for each format’s authentication details.

Yes — per-partner ceilings sized for normal distribution traffic with burst tolerance for backfills and reprices. We respond with standard 429 + Retry-After when a ceiling is hit. If your workload needs a higher ceiling (large multi-property catalogs, for example), tell us during the technical call and we’ll provision accordingly.

Book a 30-minute technical call. We walk through the spec, confirm the channels and integration model you need, and provision sandbox credentials — typically within 24 hours of the call. The sandbox runs against real endpoints, not a toy environment.

The JSON API is versioned in the path (/api/v2/). Breaking changes get a new major version with a deprecation window measured in quarters, not weeks — so you have time to migrate. New OTAs and capabilities ship as additive endpoints on the current version, no migration required to pick them up.

No. No per-channel certification fees. No per-integration setup fees. The integration time investment is on your side; on ours, you pay the regular monthly subscription. Every channel we support is included in your plan.

Yes, as a Powered by ChannelRUSH partnership. Your product, UI and brand are what your hotels see, they manage distribution inside the PMS they already use, and you own the customer relationship. The channels connect to ChannelRUSH, so our name appears at the channel level, for example in an OTA's extranet. See PMS partnerships for how it works.

Yes. Regional, revenue and front-desk staff get their own logins, each limited to the properties you assign and the permissions their role needs. Two-factor login is available, and every change is logged against the user who made it.

Guides and definitions