Scheduling & Booking · Integration
apaleo
Add apaleo to your product for your customers, and give your AI agents governed access to it.
apaleo is an API-first hotel property management system, and everything is scoped by property code: api.apaleo.com returns 401 without a token, and once authenticated almost every list call expects a propertyId, so a customer with several hotels is several scopes rather than one dataset. Authentication is OAuth 2 with fine-grained scopes such as reservations.read and rates.read, and an integration that asks for too narrow a scope set fails at the endpoint rather than at connect time, which is easy to miss in testing. The model separates a booking from the reservations inside it, so a single guest booking can hold several reservations across dates, units and rate plans, and code that treats one reservation as one stay will misreport occupancy. Availability is computed against unit groups rather than individual units, and a unit is only assigned close to arrival, so plans that key on a specific room number early break. Financials sit in folios with charges and payments that post independently of the reservation status. fastn holds each customer's apaleo OAuth grant and property scope on their own connection and refreshes tokens without staff intervention.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own apaleo property so arrivals and departures appear in your product automatically
Show tonight's in-house guests and unassigned reservations for each property in one view
Post charges to the correct folio from your ancillary service so they settle at checkout
Read rate plans and unit group availability to quote a stay without duplicating the hotel's pricing rules
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which reservations arrive today at a given property and which have no unit assigned
Have an agent summarise folio balances for departing guests, with every read audited per tenant
Let an agent flag bookings whose reservations span rate plans that no longer exist
Example prompt
Who is arriving at our Berlin property today and are any rooms still unassigned?
Set up apaleo in 4 steps
- 01Enable the apaleo connector from your fastn dashboard.
- 02Have each customer authorise their own apaleo account, so calls run under their credentials rather than a shared key.
- 03Decide which bookings, events and availability your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the apaleo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an apaleo integration without building it. Your customers connect their own apaleo account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an apaleo update is not your on-call problem.
- One integration serves your product and your agents. The same governed apaleo connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to apaleo, across other categories.
apaleo integration FAQ
How do I add an apaleo integration to my product?
Enable the apaleo connector in your fastn dashboard, then let each customer authenticate their own apaleo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no apaleo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own apaleo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own apaleo account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this apaleo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which reservations arrive today at a given property and which have no unit assigned
Who maintains the apaleo integration?
fastn does. When apaleo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in apaleo automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in apaleo?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the apaleo integration?
A common starting point: let a customer connect their own apaleo property so arrivals and departures appear in your product automatically. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the apaleo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding apaleo does not change your per-connector cost. You can start free with 3 connected accounts.
Add apaleo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.