Central Reservation System API
One API. Every PMS, booking engine, and OTA.
A fast, secure REST API that lets your PMS, booking engine, OTAs, and internal services push and pull availability, rates, and reservations against the CRS in real time.
Hotel CRS API for Multi-Property Portfolios
Unify reservations, rates, and availability across every property and channel with a fast, modern JSON REST API — built to integrate cleanly and scale reliably with your tech stack.
Instant updates to inventory, restrictions, and reservations keep every channel aligned and help prevent overbookings. Create, modify, and cancel reservations against live availability and rules — centralize logic once; propagate everywhere.
Book a Demo
Every feature in the admin
is also a public endpoint.
Auth is OAuth 2.0 with portfolio-, brand-, and property-scoped tokens. Every write emits a versioned audit record and an optional webhook.
Reservations API
Create, modify, and cancel reservations against live availability and rules — every write is versioned.
Availability API
Portfolio-wide inventory and restrictions — query and update every property from a single endpoint.
Rates & Restrictions API
Rate plans, length-of-stay rules, and date-based policies — inheritable from brand down to property.
Content & Channel Profiles API
Property descriptions, images, amenities, and channel mappings — kept consistent across every surface.
Webhooks API
Versioned event stream for reservations, rates, and audit events — with retry history queryable via Admin & Audit.
Admin & Audit API
User actions, IP-attributed system logs, and webhook delivery history — the record of who did what, and when.
Unlock Results with an Enterprise Hotel CRS API
The ChannelRUSH CRS API gives multi-property brands a single source of truth and real-time control. Connect your PMS, RMS, CRM, brand.com, OTAs, and partner tools to one reliable data model so pricing, content, and availability stay perfectly in sync.
Reservation lifecycle: create, modify, cancel with live validation against rules and inventory
Portfolio-wide consistency: standardize rate plans, policies, and content across every property
Open & modern: clean JSON REST endpoints, webhooks, and clear docs for faster integrations
Operational confidence: audit logs, role-based access, and error handling reduce manual fixes
The result: fewer discrepancies, fewer overbookings, and a smoother guest experience — delivered at enterprise scale.
Book a Demo
Every reservation, every version, kept.
Your CRS is the book of record for every reservation your brand takes — we treat it like one. Every reservation carries a full version history — created, modified, cancelled — with the channel source, guest, rate, and restriction state at each step.
Every API call and every admin action is logged with user, IP, and timestamp. The audit log is streamable over webhook, so your data warehouse and your compliance tooling see the same events we do.
Rate, channel source, guest, and restrictions captured at time of booking
Cancel reason, cancelling user, IP, and timestamp on every revision
Admin portal actions logged alongside API writes — one unified trail
Webhook delivery history with retries and final disposition
GDPR- and PCI-DSS-compliant retention by default
What You Can Build
Custom Booking Experiences
Mobile Apps & Upsells
Operations & Admin
Ready when you are
Let's see if we're your perfect partner.
Drop us a line and we'll set up a 20-minute walkthrough of the platform against your stack.
How integrations actually
work with us.
Named engineer, day one
Tell us about your stack, your timeline, and your constraints. A ChannelRUSH integration engineer owns your project from the first call to production.
Sandbox in one business day
A full CRS sandbox, provisioned within one business day. Test data, scoped API keys, live webhooks — the same surface you'll ship against in production.
Design review before you ship
We review your integration design before go-live — auth scope, webhook retry handling, versioning strategy. Two-week typical time-to-first-reservation.
Ready to see it in action?
Frequently Asked Questions
Every reservation carries a full version chain. Each write — create, modify, cancel — records the channel source, user, IP, timestamp, and the full state of the reservation (rate, guest, restrictions) at that moment. Versions are immutable; a cancellation writes a new version rather than overwriting history, so finance and compliance teams can reconstruct what happened and when.
OAuth 2.0. Tokens scope to the portfolio, a single brand, or a single property — the same hierarchy the admin uses. A partner PMS typically holds one brand-scoped token; a travel management company might hold a property-scoped token per hotel they manage. Full reference at our API documentation.
Webhooks fire on reservation create / modify / cancel, rate and restriction changes, and audit events. Failed deliveries retry with exponential backoff over 24 hours; delivery history (including retries and final disposition) is queryable via the Admin & Audit API so you can reconcile any gap without guesswork.
Rate limits are applied per API token and vary by endpoint class (reads are more generous than writes). When you're throttled the API returns 429 Too Many Requests with a Retry-After header so your client can back off cleanly. High-volume partners work with our integration engineers to size limits to their specific workload rather than retrofit around defaults.
Yes. Release notes are published alongside the API reference and list every additive change, bugfix, and deprecation. Breaking changes are announced ahead of time and shipped behind versioned endpoints so your integration has a clear window to migrate — not a surprise cut-over.
Inbound writes are queued until the upstream system recovers. Outbound webhooks retry on the standard backoff schedule. The interruption shows up in the audit log as a delivery gap with its final disposition — you see the same picture we see, and no bookings are lost in the silence.