API · Connected

Custom APIs

Any system with a REST or GraphQL API can be connected to Casa Layer. We build custom connectors for non-standard stacks.

What Casa Layer reads

Any structured guest data

The connection

Reads via: REST or GraphQL
Direction: Casa Layer reads guest data from your Custom APIs. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
Status: Connected

What this takes from you

Vendor approval: The partner side is already in place. You authorise the access from your own Custom APIs 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 Custom APIs 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

Other integrations

See Casa Layer in practice

A 20-minute demo covers how Casa Layer connects to Custom APIs 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