Create a developer account on the Apaleo developer portal and register your application to receive OAuth 2.0 client credentials; sandbox access is available without a sales process
Implement the OAuth 2.0 client credentials flow for server-to-server calls, or authorization code flow for integrations acting on behalf of a hotel account
Explore available endpoints using the Swagger UI at api.apaleo.com, which allows authenticated test calls directly from the browser against the sandbox
Query reservations using the Booking API, noting that Apaleo models a booking as a container for one or more reservations, each covering a single room
When creating a reservation from a channel, store the external booking reference in the externalId or the appropriate ExternalReferences field (channelManagerId, onlineTravelAgencyId, etc.) to maintain cross-system traceability
Post charges to a guest account using the Finance API endpoints by referencing the reservation and specifying the service and amount
Known gotchas
Apaleo's pricing model requires specifying the correct total price per stay date inclusive of VAT; submitting prices exclusive of tax without adjusting the tax flag causes incorrect folio totals for guests
Apaleo uses separate APIs for property management (properties, units, rate plans) and booking (reservations, folios); confusing which API family to call for a given operation returns 404 or 400 errors
Sandbox credentials do not work against production endpoints; the environment is controlled at the OAuth token issuer level, so using a sandbox token against production results in authentication failures, not data isolation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp