Integrations
Table Booking · Ready to build
Square Bookings
Pull customers and bookings from your Square account.
What Casa Layer reads
- Customers
- Bookings
The connection
- Direction
- Casa Layer reads guest data from your Square Bookings. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
- Status
- Ready to build
- Website
- squareup.com
What this takes from you
- Vendor approval
- We confirm this with Square Bookings before any work starts. Some vendors open their API to any customer, others require a signed partner agreement first. We tell you in writing which one applies to you.
- Cost to you
- Nothing from us. Building and running the connection is part of the platform licence, not a separate integration fee. If Square Bookings 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, once Square Bookings access is approved. We scope the exact date with you before you commit to anything.
- 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 a Square account with an access token. Casa maps each Square location to a Casa property and pulls customers and bookings.
What syncs
Customers and bookings (time, status, linked guest).
Use cases
Attach spa and appointment spend to the same master profile as hotel stays.
See Casa Layer in practice
Square Bookings is not connected for anyone yet, but the API exists and we have the pattern: about three weeks from your go-ahead. A 20-minute demo shows the layer running on a built connection, and we scope Square Bookings against your stack on the same call.
Book a 20-minute demo