Integrations
Table Booking · On the roadmap
OpenTable
Restaurant reservation records and covers ingested from OpenTable, with diner identifiers matched against the guest profile.
What Casa Layer reads
- Reservations
- Covers
- Diner identifiers
The connection
- Reads via
- OpenTable API
- Direction
- Casa Layer reads guest data from your OpenTable. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
- Status
- On the roadmap
- Website
- www.opentable.com
What this takes from you
- Vendor approval
- OpenTable opens this API to approved partners only, so a signed vendor partner agreement has to be in place before the connection can run. We handle that application; you confirm you want it.
- Cost to you
- Nothing from us. Building and running the connection is part of the platform licence, not a separate integration fee. If OpenTable 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
- Not built yet, so we will not give you a date we cannot hold. Tell us you run OpenTable and we will tell you honestly where it sits in the queue.
- 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
We have not built OpenTable yet
OpenTable is on the roadmap, not connected, so there is nothing to demonstrate on it today. If you run OpenTable, tell us: the systems our customers ask for are the systems we build next, and we will tell you honestly where it sits in the queue.
Ask us for OpenTable