Education · Integrations
Four systems. One guest. No universal hotel API.
A request to “integrate with the hotel” is incomplete. The reservation, room, restaurant check, and valet charge may live in different systems with different owners.
The map
Start with the business event, then find its system of record.
If the goal is to post valet to a room folio, ask where folios live. If the goal is to anticipate arrivals, ask where reservation status is authoritative. Acronyms matter only because they narrow that conversation.
The glossary
What each layer generally owns
Property Management System
Rooms
Stay state
Check-in, checkout, room assignment, and core guest-stay operations.
Folio
Guest account
Charges and payments accumulated against the stay.
Profile
Guest context
Identity and preferences governed by the property's processes and permissions.
Operations
Property workflow
Housekeeping, front-office, and related status depending on the system.
Point of Sale
The restaurant, spa, shop, or outlet often closes its own checks here.
A POS can be relevant when dining validates parking or when a property wants outlet charges and parking to reconcile. It is not automatically the authority for a room stay.
Central Reservation System
The CRS distributes and manages reservation inventory across channels and properties.
It can be useful for future arrival context, but a booking record is not the same thing as an in-house guest or an open folio. Integration design must respect that change of state.
Integration layer
Modern hotel groups may expose approved interfaces through a separate platform.
→An accepted API call is not enough; the valet operation needs to know whether the hotel accepted the business event.
As one current example, Oracle describes its Oracle Hospitality Integration Platform as the API platform for OPERA Cloud. That is a vendor-specific example, not a synonym for every hotel integration.
The first integration question
Which system owns the truth we need to change?
Once that answer is explicit, the rest becomes engineering: identity matching, permissions, retries, acknowledgments, and reconciliation. Without it, teams can connect two systems perfectly and still connect the wrong facts.
Write a one-page event contract before discussing vendors. For a folio post, name the guest or stay identifiers supplied, the amount and description, when the post is allowed, what a duplicate means, which response counts as acceptance, and who sees a rejection. For a departure signal, name the source state, update frequency, and what valet may infer. That document keeps the hotel objective visible when API details become complicated.
Version that contract with the integration. Hotel upgrades and mapping changes should not silently alter the business meaning.
