ChannelRUSH API Documentation
– API specs, integration guides, developer references
Build against ChannelRUSH to distribute inventory, receive reservations, power booking pages, and automate rate & availability messaging. Full specs live on help.channelrush.net.
Channel Manager APIs
For adding channel-manager capabilities to your software platform — distribute rates, availability, and inventory (ARI) to points of sale like Booking.com and Expedia, and retrieve the reservations they produce.
- Push ARI to OTAs and GDS points of sale
- Retrieve new, modified, and cancelled reservations
- Two spec formats — JSON (recommended) or XML (OpenTravel.org)
Channel Manager PMS API – JSON Spec
Modern JSON-over-HTTPS interface for pushing ARI and pulling reservations. The path we recommend for new integrations.
Channel Manager API – XML Spec
Same functionality as the JSON spec, expressed in the XML OpenTravel.org schema. Use this if your platform already speaks OpenTravel.
OTA (Online Travel Agent) APIs
Two models for booking reservations through ChannelRUSH — the CRS model (pull content and query rates / availability in real time, then book) or the OTA model (ChannelRUSH pushes ARI messages to an endpoint on your side, and you push or expose reservations back).
CRS API
Real-time booking from your platform: pull property content for booking pages, query live rates and availability, search properties by location, and place reservations.
OTA API
You expose an endpoint on your side to receive rate / availability / restriction messages plus setup and reservation-action calls. Push reservations back, or let us poll for created / modified / cancelled bookings.
Developer support
Our integrations team pairs with your developers on spec questions, sandbox access, and edge-case behavior.
Drop us a note — humans answer, not a triage queue.