Connectivity & integrations
How rates, rooms and availability move through the platform.
We receive rates, rooms and availability from each hotel's property management system, hold them as a single source of truth, and publish them to the hotel's own booking pages and to structured distribution feeds.
We build integrations against each property system's published API. New systems are added as hotels need them.
Your system stays in charge.
Your rooms, rates, restrictions and availability are read straight from the property management system your team already works in. Nothing is retyped, and there is no second system to keep in step.
Cloudbeds is live across the portfolio. Integrations with Mews and Oracle OPERA are built against the same interface, with OPERA certification in progress. Changes reach us as they happen rather than waiting for a scheduled sync, and we build new integrations against each system's published API as hotels need them.
One set of numbers, everywhere.
Your rates live in one place. Your booking pages, your structured data and everything we publish outward all read from it, so they cannot quietly disagree.
Prices are calculated when a guest searches rather than served from a cache, and the price is re-checked before any personal details are asked for. What a guest is quoted is what they pay.
Change a price, and only that price moves.
Drop your rate for one weekend and that weekend is what updates, not your whole calendar, and not on tonight's batch run. Every night of every rate plan is tracked individually, so only what actually changed is sent onward.
A nightly reconciliation checks the full year against what has been published and reports any disagreement. Failed deliveries retry, then escalate to a person.
Your prices, out where guests are looking.
We build and maintain the rate, availability and inventory feeds that distribution and metasearch channels require, in the format those channels publish — OpenTravel 2003/05, version 3.0 — and keep them in step as your prices move.
Feeds carry a full 365 days, priced before and after tax according to your property's own tax position, with your cancellation policies attached to each rate plan and every occupancy priced rather than just the default.
Guests land on the room they clicked.
Someone who finds your rate on an external channel arrives on your own website, on those dates, on that room, at that price, ready to book. Not on your homepage to start again, and not routed through anybody else's domain on the way.
Pages are rendered server-side with real prices in the HTML, so a search engine or an assistant reading the page sees the same number the guest does.
The booking arrives like any other.
When a guest books, the reservation is created in your own system through the same connection the rates came from — extras on the folio, payment recorded against the booking, and any guest requests written on it.
Your team works the way it already works. A direct booking sits in the same place as an OTA booking, and nobody has to log into ours. A closed browser mid-payment, a duplicate notification or a retry cannot produce a second reservation — we check your system before writing anything to it.
| Property systems | Cloudbeds (live) · Mews (integration built) · Opera (integration built, certification pending) |
|---|---|
| Rate messaging | OpenTravel 2003/05, version 3.0 |
| Distribution feeds | Property · Rate · Availability · Inventory |
| Payments | Stripe Connect · hotel as merchant of record |
| Booking pages | Per-hotel domain, server-rendered, no redirect on entry |
| Rate horizon | 365 days |
Integration enquiries
Property management system vendors and distribution partners wanting to discuss an integration should contact the technical team.