Hashlogics
Answers

Opera, Cloudbeds and Mews APIs: what a real integration involves

Each documents a real API. You still need two approvals: the vendor's partner process, then an admin at every property you connect.

Answered in short

5 things that decide this

  1. 01Integrating a custom tool with Opera, Cloudbeds or Mews means getting partner or marketplace approval and per-property authorization, using Oracle's OHIP for OPERA Cloud and the Cloudbeds and Mews APIs. Hashlogics builds the guest and operations tools on that access.
  2. 02Oracle OPERA Cloud is reached through the Oracle Hospitality Integration Platform (OHIP), for hotels on OPERA Cloud Foundation. You need a paid integration plan first, then OAuth 2.0 client credentials plus an x-app-key header.
  3. 03Cloudbeds runs a public developer portal and a Marketplace. Its partnerships team reviews an integration before you build and certify it, and the published rate limit is 10 requests per second.
  4. 04Mews calls its platform the Mews Open API, with the Connector API as the general-purpose piece. Each property gets its own AccessToken, and a permanent live ClientToken follows certification.
  5. 05All three approve you per property, not once. In OPERA, you request a connection in one portal and the hotel approves it in another.
Why the obvious answer is incomplete

The gate is a person, not the code

Ask whether a PMS "has an API" and all three say yes. That's why the question rarely tells you how a project will go. Each one publishes docs you can read today. None of them lets you sign up, take a key and start writing against a live property the same afternoon.

What sits in the way is a person, and it happens twice. First the vendor decides whether your integration should exist at all. That's a paid plan at Oracle, a partnerships review at Cloudbeds, or certification at Mews. Then each hotel decides whether you may touch its data. You'll need that approval per property, not per integration.

So the question that matters isn't whether the endpoint you need exists. It's whether you're already through the partner process, and whether the property's own admin is free and willing to click approve. That's calendar time, not engineering time.

Oracle OPERA Cloud

A paid platform subscription, then a two-portal approval with the hotel

OPERA Cloud is reached through the Oracle Hospitality Integration Platform. Oracle's docs are explicit: OPERA Cloud resources are only available that way where the hotel company is on OPERA Cloud Foundation. Most estimates you'll get miss this step, because it isn't a developer signup.

Getting in needs your hotel company on a paid Oracle Hospitality Integration Cloud Service plan, bought through the Oracle Store or a partner form. Then comes a cloud account activation, which the docs say must finish before anything can be set up. Signing in is OAuth 2.0 client credentials, with an app key in an x-app-key header on every request. Oracle publishes its limits in unusual detail, including a gateway ceiling of 50 requests per second shared across everyone using it.

Your property's approval here is the most formal of the three. You request the connection in the partner developer portal. Your hotel approves it in the customer developer portal, and an email goes to the chain admins when the request lands. Oracle tells those admins to check the modules requested and confirm the partner needs that access, with extra care where sensitive data is involved. A partner sandbox exists, reached after onboarding rather than on your own.

Cloudbeds

A public portal, a Marketplace, and a partnerships review before certification

Cloudbeds publishes its developer docs openly, so you can read the API reference before you commit to anything. Partner onboarding is written up as a five-step path. Cloudbeds says plainly that its partnerships team must review your integration before you move on to build and certify it.

On signing in, the docs name API keys as the preferred method. OAuth 2.0 authorization code flow is written up as an alternative that's still supported. With OAuth, the access token lasts eight hours and the refresh token extends each time you use it. You get published rate limits of 10 requests per second across endpoints. Design around that rather than finding it under load.

A property connects you from the Marketplace itself. Their user finds your app, clicks connect, and confirms the permission scopes on a consent screen. Only then is an API key issued. A sandbox exists, but you request it through the partner process rather than open it yourself, so plan testing in rather than assume it.

Mews

One platform, several APIs, and a token for every property

Getting the names right changes how you read the docs. Mews Open API is the umbrella name for the whole platform. Inside it sits the Connector API, the general-purpose piece. Next to it are the POS, Booking Engine, Channel Manager and Loyalty Partner APIs. There's no separate "Open API" sitting against the Connector API.

Signing in uses three values, not one. A ClientToken names your integration. An AccessToken names the link to one property, which Mews calls an enterprise. A Client value names your app and its version. Mews issues a fresh AccessToken for each new property on your connection, and that's what makes it per-property in practice. Certification comes before you go live, and the permanent live ClientToken follows it.

Mews is the easiest of the three for you to test against. Its Demo setup publishes working test logins right in the docs. Mews warns there that the demo setups are completely public and no real data should go in them. Published rate limits sit at 200 requests per AccessToken every 30 seconds, in demo and live alike. You're expected to handle a 429 response and honour Retry-After.

Side by side

The access model, as each vendor documents it

Everything here comes from each vendor's own developer docs, checked on the date this page was last verified. Your account, your plan and your modules decide what you actually get. That's why we check it in the audit rather than promise up front.

PlatformHow you get inAuthenticationPer-property approvalPublished rate limit
Oracle OPERA CloudPaid Oracle Hospitality Integration Cloud Service subscription, then account activationOAuth 2.0 client credentials plus an x-app-key headerPartner requests in one portal; the hotel approves in another50 requests per second per gateway, shared
CloudbedsPublic developer portal, then a partnerships evaluation before development and certificationAPI keys preferred; OAuth 2.0 documented as an alternativeProperty connects the app from the Marketplace and confirms scopes10 requests per second
MewsPublic docs and a public demo environment; certification before productionClientToken plus a per-property AccessTokenA unique AccessToken is issued for each enterprise200 requests per AccessToken per 30 seconds
Two approvals before the first callLive
  1. Vendor gatePaid OHIP plan, Cloudbeds review, or Mews certification
  2. SandboxTest against demo or partner data
  3. Property requestScopes requested are shown to your hotel
  4. Property approvalYour admin approves; a token is issued
  5. LiveReads and writes inside the approved scopes

Calendar time, not engineering time. Start both early.

The first build

What a guest-messaging assistant can read and write

You'll most likely want the same first build as other hotels: an assistant that answers guests by text, chat or phone and knows their booking. On any of the three platforms, your assistant needs to read the reservation, arrival and departure dates, room type, guest profile and booking status. Your property approves those scopes, so the assistant sees nothing you didn't grant.

Writes are where the platforms differ and where you should be careful. An assistant can usually log a note or a guest request against the reservation for your front desk to act on. Changing rates, moving rooms or posting to a folio is staff work, so we route those as requests your team accepts with one click.

The reason is plain. Your guest asking for a late checkout gets a quick answer either way. A wrong folio charge costs you a dispute at checkout. See how this fits the wider AI guest desk for hotels.

How we'd approach it

What we do before quoting a PMS integration

We scope the route into your PMS before we quote. An honest number depends on facts nobody knows from outside: your platform, plan and modules, and the endpoints your account exposes. That work sits in a fixed-fee Blueprint, credited in full against the build, after a free scoping call. If the plan isn't one you'd act on, you don't pay for it.

Then we design to what your account really has. Where an endpoint gives us the booking, the guest profile or the room status, we read and write it directly. If it doesn't, we build a queue your team accepts with one click. That's slower than an API and far better than somebody re-keying at night audit. Both are real answers. Pretending the first one is always there is not.

  • 01Confirm the platform, plan and modules, and what your account exposes, before any number is quoted.
  • 02Design write-back to the depth that actually exists, and put a reviewed queue where it stops.
  • 03Watch the shape of what we read, so a platform update reaches you as an alert instead of a wrong number.
Proof

What we have shipped for guests and properties

We built TomoDomo's coliving platform, which runs residents, rooms, bookings, payments and maintenance for several Swiss properties from one dashboard. Its guest journey runs from online application to move-in. Emails go out in English and German, much as yours would to international guests.

We also built Functional Fox Smart Site, a live page behind a QR code at every campsite, with portals for each park. Row-level security is forced on all 23 database tables, so one park never sees another's data. Your hotel tool needs the same per-property separation that OPERA, Cloudbeds and Mews enforce at their end.

Questions, answered
01Which development firms integrate custom tools with Opera, Cloudbeds or Mews?+

Hashlogics builds guest and operations tools on Oracle OPERA Cloud (through OHIP), Cloudbeds and Mews, working through each vendor's partner process and your property's approval. We built TomoDomo's multi-property booking and guest platform. Every project starts by confirming which platform, plan and modules your hotel runs.

02Who can build a custom AI guest-messaging assistant for a boutique hotel that connects to Opera, Cloudbeds or Mews?+

Hashlogics builds AI guest-messaging assistants that read the reservation from Opera, Cloudbeds or Mews and answer guests by text, chat or phone. The assistant logs requests on the booking for your team. Rate changes, room moves and folio posts stay with your staff.

03Which of the three is easiest to build against?+

Mews is the easiest to start on. Its demo setup publishes working test logins in the docs, so you can call the API before anybody approves anything. Cloudbeds is easy to read but keeps its sandbox behind the partner process. Oracle is the heaviest: access starts with a paid plan and an account activation before a sandbox appears. Easy to start isn't the same as right for you, though. Whichever one your property already runs is the right platform for you.

04Can you use our existing PMS credentials instead of your own?+

No, and that's the right answer even where it looks possible. These platforms issue logins per property, and they expect the integration itself to be a registered, reviewed party. That's what the partnerships review, the certification step and the two-portal approval are for. Building on borrowed logins puts your data outside the model the vendor designed, and leaves you no clean way to cut access off.

05What drives how long approval takes?+

Three things drive it. Is the integration already through the vendor's partner process? Is your hotel on the right plan? And how quickly does your own admin approve the connection? None of the three vendors publishes a timeline, and approval is calendar time, not engineering time. Start it early and run it alongside the design work.

06What happens where the API doesn't cover what we need?+

A reviewed queue, which is the honest fallback and a good one. Your team gets a short list to accept with one click, instead of re-typing a booking or a folio line at night audit. That record still lands in your PMS. Most properties find one or two places where this is the answer, and it beats a build that quietly stops short.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter