Integrations
Every system we connect to, and where each one stands.
Casa Layer reads from the systems your hotel already runs. They stay where they are, so there is nothing to rip out and no migration project, and we unify them into one Master Profile every agent can run on. Each system below says plainly whether the connection is built, ready to build, or on the roadmap.
Directory
Sources
- PMS
- POS
- SPA
- TABLE BOOKING
Consumers
- REST API
- MCP
- YOUR CRM
- GUEST APP
- 3Connected
- Built and running. We can show you this connection working on a call.
- 4Ready to build
- The API exists and we have the pattern. About three weeks from your go-ahead.
- 23On the roadmap
- Not started. Tell us you need it and it moves up the list.
Counts every system in the directory below, in both directions. Every connection lands in the same Master Profile, and agents read that record back out over the MCP server.
Directory
One directory, both directions.
The systems Casa Layer reads guest data from, and the ones that read the Master Profile back out: your team, your CRM, a guest app, and any agent. Filter by category, or scan the lot.
30 systems
PMS
Apaleo
Property reservations, guest accounts, and rate plans read via the Apaleo REST API with live webhook support.
PMS
Clock PMS
Guest profiles, stay history, and folio data synced from Clock PMS+ via the Clock REST API.
PMS
Cloudbeds
Sync guests and reservations from Cloudbeds.
PMS
Guestline
Reservation, profile, and rate data read from Guestline Rezlynx via the Guestline partner API.
PMS
Mews
Reservation data, guest profiles, and folio details synced in real time via the Mews Connector API.
PMS
Oracle OPERA
Stay history, room type, rate code, and guest profile pulled directly from OPERA Cloud and OPERA 5 via the REST API.
PMS
Protel
Stay history and guest records imported from Protel Air and Protel On-Premise via the Protel API.
PMS
Stayntouch
Sync guests and reservations from Stayntouch.
POS
Lightspeed
Food and beverage spend, dietary notes, and table preferences read from Lightspeed Restaurant via the Lightspeed API.
POS
Toast
Pull restaurant orders and guests from Toast POS.
Spa
Book4Time
Spa and wellness appointment history, treatment preferences, and guest spend read from Book4Time via the Book4Time API.
Table Booking
OpenTable
Restaurant reservation records and covers ingested from OpenTable, with diner identifiers matched against the guest profile.
Table Booking
ResDiary
Restaurant bookings, dietary notes, and dining history read from ResDiary via the ResDiary API.
Table Booking
SevenRooms
Restaurant reservations, dining preferences, and guest visit history read from SevenRooms via the SevenRooms API.
Table Booking
Square Bookings
Pull customers and bookings from your Square account.
Table Booking
Zenchef
Pull restaurant reservations and diners from Zenchef.
Housekeeping
Flexkeeping
Guest requests, room and cleaning status, and service history read from Flexkeeping's housekeeping and maintenance suites.
Housekeeping
Sweeply
Guest requests, room and cleaning status, and task history read from Sweeply, so the profile carries what happened during the stay and not only what was booked.
Reputation Management
GuestRevu
Pull guest feedback and survey responses from GuestRevu.
Reputation Management
MARA AI
Bring in guest reviews and AI reply insights from MARA.
Reputation Management
Reva
Pull guest reviews and reputation data from Reva.
Guest Management
Alliants
Sync guest profiles and messaging from Alliants.
Guest Management
Duve
Sync guest profiles and stay data from Duve.
Guest Management
Revinate
Sync guest profiles and campaign data from Revinate.
CRM
Klaviyo
Email and SMS engagement, campaign activity, and marketing profile attributes synced with Klaviyo, so every agent works from the same guest context.
CRM
Mailchimp
Email engagement, campaign activity, and audience fields from Mailchimp, so every agent works from the same guest context.
AI Agents
D3x
Casa Layer serves the Master Profile to D3x's hospitality agents, which resolve guest requests across WhatsApp, voice and email.
AI Agents
Onsai
Casa Layer serves the Master Profile to Onsai's digital hotel agents, which handle calls, chat and email in the guest's own language.
API
Claude
Claude and other AI agents read the governed Master Profile over Casa Layer's MCP server, acting on complete guest context in real time. Casa serves the profile; the agent runs on it.
API
Custom APIs
Any system with a REST or GraphQL API can be connected to Casa Layer. We build custom connectors for non-standard stacks.
- 01
Access you grant
You decide what Casa Layer can do in each system, under credentials you issue and can revoke. An agent that can only read can only advise, so write access is being built too. Every connection live today reads only, and write access stays off in a system until you switch it on there.
- 02
Historical backfill
On first connection we import your full stay history so day one is not a blank slate. Guests who stayed five years ago are part of the Master Profile from the start.
- 03
Live sync
After backfill, new reservations and transactions flow in continuously. The Master Profile updates as new data arrives from each connected system. A first connection takes about three weeks from your go-ahead.
The layer every agent runs on
- 01
Open REST API
Every Master Profile is available through a documented REST API. Your team, your CRM, and your guest app read the same record.
- 02
MCP server
Any agent (Claude, a revenue agent, or a third-party tool) connects through the MCP server and acts on the same ground truth, with no bespoke integration per agent.
- 03
The record outlasts the agents
The agents will change every year; the record they run on sits outside all of them, not trapped in a vendor suite. We sell no agents of our own, so it is not shaped to favour one.
Using a system not on this list?
Using a system not on this list?
If it has an API, we can connect to it. Tell us what you are running and we will tell you what the connection takes and how long it takes, before you commit to anything.