Open PMS API

Connect any PMS — or the integration platform between your PMS and other systems — without waiting for a built-in connection. The PMS sends each reservation to one web address whenever it changes; rooms, TVs and guests' phones follow. Mews and Apaleo have their own connection (PMS) and do not need this.

Reference: Open PMS API reference · OpenAPI file

#How it works

• State, not events. Send the whole reservation every time it changes — status, room, dates, guest. Sending the same reservation twice, or two updates in the wrong order, gives the same result: the last state wins.

• What each status does

  status	What happens
  booked	The stay gets a guest link for before arrival (with the room type if you send it)
  in_house	The guest is checked into room: the TV greets them by name, the phone app opens, room devices get the guest's settings
  checked_out	The guest is checked out: the TV clears the guest's history and app logins and turns its screen off, phones are disconnected
  canceled, no_show	The guest link closes

• Rooms by number, room types by name — exactly as written in the console (Settings → Property). Moving a guest is an in_house update with the new room.

• Guest names are used only to greet the guest on the TV while in house. The console shows only the first letter (J***), and the name is deleted at check-out.

#Set up the connection

1. In the console, Settings → Integrations → PMS, open the Open PMS API tab and press Connect Any PMS (Open PMS API). Give it a name and Save — it is on (only one PMS can be on at a time).
2. Press Use the room numbers here once — it lists the console's room numbers and room types as the ones the PMS will send (done again by itself with every message, so new rooms are picked up).
3. Copy the webhook address and give it, with this page, to whoever runs your PMS. The address is the password: keep it out of public places; New address replaces it at once.
4. Send a test event checks the address. The connection's log lists every message and what it did.

#Send a reservation

POST the reservation to the webhook address with Content-Type: application/json:

POST https://nnilcrwcusuhmauixpaf.supabase.co/functions/v1/integrations/v1/hooks/{key}
Content-Type: application/json

{
  "reservation": {
    "id": "R-10045",
    "status": "in_house",
    "room": "632",
    "roomType": "Suite",
    "arrival": "2026-10-25",
    "departure": "2026-10-27",
    "guest": { "name": "Jane Doe", "language": "en" }
  }
}

Several at once (up to 100) — for example after the PMS was offline:

{ "reservations": [ { "id": "R-10045", "status": "checked_out", "room": "632" }, { "id": "R-10046", "status": "booked", "roomType": "Deluxe", "arrival": "2026-11-02", "departure": "2026-11-05" } ] }

Answers

A GET on the address answers 200 — for a PMS's "test connection" button.

#curl

curl -X POST "$WEBHOOK" -H "Content-Type: application/json" \
  -d '{"reservation":{"id":"TEST-1","status":"in_house","room":"632","guest":{"name":"Test","language":"en"}}}'
curl -X POST "$WEBHOOK" -H "Content-Type: application/json" \
  -d '{"reservation":{"id":"TEST-1","status":"checked_out","room":"632"}}'

#Good practice

• Send on every change the PMS makes: booking, room assignment, check-in, room move, extension, check-out, cancellation.
• Retry on a timeout or a 5xx — a retry is always safe.
• The connection's log in the console shows Skipped with a reason when a room number is not known here, or a guest is in house without a room — fix the room in the console or the PMS and send the reservation again.
• A guest checked in from the console is never checked out by the PMS.