Connect the hotel tech stack once.
Hotels connect their PMS, CRM and guest platforms to Corella once. Solution providers read and write that data through one API, within the permissions each hotel sets.
- OPERA CloudreservationsArrivals today6 still without a room38
- OPERA CloudhousekeepingRooms to clean9 needed for 15:00 check-ins14
- MessageBoxopenRequestsOpen service requests2 past their SLA11
- ReviewProreputationDailyReview index, yesterdayCleanliness down 2.187.4
- SalesforceopportunitiesGroup enquiries in progress2 for dates this month5
Example figures, each read from its own platform through the same API.
- MessageBox
Every platform in. One API out.
A hotel connects its platforms once. Corella keeps the data fresh and hands it to the solutions the hotel uses, for every team that needs it.
Connect once
Corella tests and seals the credentials, backfills history, then keeps the data fresh.
- Hotel ID
- GRANDPALACE
- Client secret
- ••••••••••••
- Credentials tested
- Encrypted, never returned
- Permissions set by the hotel
Then backfills history
- Reservations2 years
- Daily revenue2 years
- Rooms, room types, rate planscurrent
Then keeps it fresh
- Open service requestsevery 10 min
- Housekeepingevery 15 min
- Reservationshourly
Once per hotel. Credentials are tested before anything is stored.
Access on the hotel’s terms
Read and write, with each hotel deciding what every solution may do.
- Permissions per action
- Corella reads and writes within the permissions each hotel sets. Every action is allowed, held for approval or denied.
- Credentials stay sealed
- Encrypted when they’re connected, decrypted only in memory, never returned by the API.
- Everything traceable
- Every request carries an ID through to the syncs it starts, and every write leaves an audit trail.
- reservations.addNoteNeeds approval
- reservations.deleteNoteDenied
- Every other writeDenied
Audit trail
- 08:41:07token:your-app · reservations.addNote → approval_required
- 08:43:52token:front-office · approved → succeeded
Example connection. Modes, decisions and statuses are Corella’s own.
Example data. Fields, backfill spans and schedules are Corella’s own.
The integration work you don’t have to do
Every hotel platform has its own API, its own limits and its own conventions. Corella takes care of them, so your product only has to work with one API.
Authentication
Each platform’s own sign-in flow, token refresh and app keys, set up and kept working for every hotel.
Pagination and rate limits
Every page read and every limit respected, with backoff when a platform pushes back.
History and changes
Up to two years of history on connect, then only what changed, including records a platform stops listing.
Failures
Errors are retried safely. A hotel whose credentials stop working is flagged, not left quietly stale.
Freshness you can check
Every response says when each kind of data last synced and whether it’s complete.
Each platform’s own data
Records keep every field the platform sends. Nothing is lost to a lowest-common-denominator model.
Works with the platforms hotels already use.
Oracle OPERA Cloud
Property management
Mews
Property management
Cloudbeds
Property management
Guesty
Property management
Hostaway
Property management
OpenTable
Restaurant reservations
- MessageBox
MessageBox
Guest requests and tasks
ReviewPro
Reputation
Salesforce
CRM and sales
HubSpot
CRM and sales
Zoho
CRM and sales
- Need another platform?Tell us which one
Built alongside the hotel tech stack, not instead of it.
Run one of these platforms? We’d like to work with you on API access and a sandbox. Talk to us.
Hotels keep the platforms they chose
Corella works with a hotel’s PMS, CRM and task tools; it doesn’t replace them or move hotels off them. The solutions built on Corella add to what those platforms do.
Access comes from the hotel
Each hotel connects each platform with its own credentials, and can withdraw them whenever it wants.
Light on your API
Published rate limits are respected. After the first sync only what changed is fetched, and Corella backs off whenever your API asks.
Open about what we call
Every connector is built from your own API specification, and we can show you exactly which of your endpoints it uses, and why.
What is Corella?
We’re a hotel. How does Corella work for us?
Which platforms do you connect to?
Does Corella replace a hotel’s PMS or CRM?
How does a hotel connect a platform?
How fresh is the data?
Can Corella write to hotel platforms?
Do you force everything into one data model?
How are credentials and data protected?
We run one of these platforms. How do we work with you?
How much does it cost?
Built for hotels and the solutions they run on.
For Hotels
Connect once. Choose any solution.
- Connect your PMS, CRM and guest platforms once, not again for every new solution.
- Decide what each solution may read or change, and approve the actions that matter.
- See every action in an audit trail, and withdraw access whenever you want.
- Keep the platforms you chose. Corella works alongside them.
For Solution Providers
Integrate with the hotel tech stack once.
- One API across PMS, CRM, task and reputation platforms, with one response shape.
- Fresh data on a schedule, live lookups when it can’t wait, and each platform’s own fields kept.
- Write back where hotels allow it, with approvals and an audit trail.
- Run a platform yourself? Work with us on API access and a sandbox.