Install Guestivo for Apaleo
Authorize Guestivo, then continue in the PMS settings workspace to link your property, import rooms, and configure folio postings for charges, payments, refunds, and external folios.
Before you start
Use a Guestivo account with hotel admin access. If you are not signed in yet, Guestivo will preserve this install flow and bring you back to PMS setup after sign-in.
What happens next
1. Sign in to Guestivo
If needed, create your Guestivo hotel workspace first. The PMS tab will open automatically when you return.
2. Authorize Apaleo
Guestivo sends you to the Apaleo sign-in page, where you approve the permissions it needs for reservations, guest bills, and payments.
3. Link the property
Choose the correct Apaleo property, import rooms, then finish your posting profiles and payment method mappings.
Recommended first checks after install
- Post a test charge to a guest folio and check it in Apaleo.
- Post a charge you collect for a partner, such as a spa or a tour, and check it lands on the right bill.
- Take a test payment and then refund it, and confirm both entries in Apaleo.
- Open a separate bill for a visitor without a reservation, add an item, then close it.
Disconnect guidance
Disconnecting takes two steps. Step 1: in Guestivo, open Admin Settings > PMS and click Disconnect. Step 2: in Apaleo, open Apps > Connected apps, select Guestivo and disconnect it there as well, so the authorization is also removed on the Apaleo side.
What the Apaleo integration covers
Guestivo is not a PMS. The integration connects the guest experience layer to Apaleo so the hotel can keep reservation, room, and folio context aligned while guests use mobile services.
Authorization and property selection
A hotel admin authorizes Guestivo through Apaleo, then selects the exact property to link inside the PMS settings workspace.
Rooms and reservations
Guestivo imports Apaleo units and uses reservation updates to support pre-arrival, in-stay, and room-context guest workflows.
Folio posting
Supported posting flows cover charges, payments, refunds, transitory charges, and external folios where the hotel enables those mappings.
Data and disconnect model
PMS access is handled server-side. When the hotel disconnects Apaleo in Guestivo, the webhook subscription is deleted, the stored refresh token is revoked at Apaleo and the credentials are deleted, stored webhook payloads, room and reservation mappings, external folio bindings and posting settings are removed, and upcoming stays that came from Apaleo are cancelled. Removing Guestivo in Apaleo under Apps > Connected apps ends the authorization on the Apaleo side as well.