Skip to content
Integrations

Housekeeping · On the roadmap

Sweeply

Guest requests, room and cleaning status, and task history read from Sweeply, so the profile carries what happened during the stay and not only what was booked.

Sweeply

What Casa Layer reads

  • Guest requests
  • Room and cleaning status
  • Task history

The connection

Direction
Casa Layer reads guest data from your Sweeply. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
Status
On the roadmap

What this takes from you

Vendor approval
We confirm this with Sweeply 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 Sweeply 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 Sweeply 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 Sweeply yet

Sweeply is on the roadmap, not connected, so there is nothing to demonstrate on it today. If you run Sweeply, 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 Sweeply