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 will redirect you to Apaleo OAuth so you can grant the PMS scopes required for reservations, folios, and payments.
3. Link the property
Choose the correct Apaleo property, import rooms, then finish your posting profiles and payment method mappings.
Recommended certification dry run after install
- Post a hotel-owned charge to a guest folio.
- Post a transitory charge to a guest or external folio.
- Post a payment and then refund it.
- Create, reuse, and close an external folio.
Disconnect guidance
Disconnect Apaleo from Guestivo in Admin Settings > PMS. Guestivo removes local property bindings and folio mappings when you disconnect.
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.
OAuth 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, Guestivo removes local property bindings and posting mappings so the workspace no longer uses that Apaleo property for guest workflows.