What Casa Layer reads
- Guest reviews
- Reputation data
The connection
- Direction
- Casa Layer reads guest data from your Reva. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
- Status
- Connected
- Website
- www.joinreva.com
What this takes from you
- Vendor approval
- The partner side is already in place. You authorise the access from your own Reva account, and scope it.
- Cost to you
- Nothing from us. Building and running the connection is part of the platform licence, not a separate integration fee. If Reva charges for API or partner access, that price is theirs to set and we give you the number before anything is built.
- Time to first record
- About three weeks from your go-ahead: connection, historical backfill, then the first resolved Master Profiles. Three weeks, not six months.
- What we do not read
- We read guest context and nothing else. Whatever the API exposes, we do not pull:
- Payment card numbers, CVV codes, or anything else in PCI DSS scope
- Rate negotiation, contract, and commercial terms
- Staff, payroll, and HR records
- Anything outside the read scope you approve before we connect
How it works
Connect Reva with account email and API key. Casa maps each Reva company to a property, then imports reviews plus the channels and spaces those reviews belong to.
What syncs
Reviews, channels, and spaces (inventory types).
Use cases
Read reputation next to stay history on the master profile, so guest context includes what they wrote after they left.
See Casa Layer in practice
A 20-minute demo covers how Casa Layer connects to Reva and the rest of your stack, resolves one Master Profile across them, and serves it to any agent through the MCP server and REST API.
Book a 20-minute demo