Each of these is a small function on StayFn instead of a separate integration project. The patterns below all use features that ship today.
For: Front office, guest relations, group operations
A function searches tomorrow’s reservations through OHIP, flags VIP guests and returns a clean list. Your intranet, reporting tool or a morning job calls it per hotel or for the whole group.
For: Guest apps, call centres, kiosks, service desks
Your applications look up reservations and profiles through StayFn functions instead of calling OHIP directly. Each app gets its own API key, scopes and quotas, and every call is recorded.
For: Revenue, guest experience, operations
When a reservation or profile changes in OPERA Cloud, a handler checks it against your rules and writes the result back through OHIP. Handlers run once per event, in order per reservation, with retries and dead letters.
For: Integration and platform teams
Systems that cannot talk to OHIP push HMAC-signed events to StayFn. A handler validates each one and turns it into an OHIP update, with idempotency so a retried event is applied once.
For: Data and analytics teams
Your pipeline calls StayFn functions on its own schedule to pull the reservation and profile data it needs, shaped for your models, without each pipeline handling OHIP tokens, limits and errors.
For: Group and regional management
One function answers for any property in the group. Hotel codes, variables and secrets live per hotel and environment, so adding a property is configuration, not code.
If OHIP exposes it, a StayFn function can usually call it: the platform covers 2,843 OHIP operations across 22 modules. Tell us what you need and we will tell you honestly whether StayFn fits.
Ask usA 30-minute walkthrough: we connect to the OHIP sandbox, write a function together and watch it run in the dashboard.