Integrations
Spa · On the roadmap
Book4Time
Spa and wellness appointment history, treatment preferences, and guest spend read from Book4Time via the Book4Time API.
What Casa Layer reads
- Appointment history
- Treatment preferences
- Spa spend
The connection
- Reads via
- Book4Time API
- Direction
- Casa Layer reads guest data from your Book4Time. 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.book4time.com
What this takes from you
- Vendor approval
- We confirm this with Book4Time 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 Book4Time 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 Book4Time 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 Book4Time yet
Book4Time is on the roadmap, not connected, so there is nothing to demonstrate on it today. If you run Book4Time, 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 Book4Time