Event & Data Hub
The Event & Data Hub is the part of LIKE MAGIC that turns everything happening across your properties (a booking coming in, a reservation checking out, a folio changing, a door opening, a task closing, a message arriving) into a stream of events that external systems can react to.
Instead of an integration having to poll the API and ask "has anything changed yet?", the Event & Data Hub lets that system subscribe once and then receive each relevant event as it happens. It is the backbone behind Webhooks & Events and behind streaming property activity into analytics and reporting tools.
This is a concept article for administrators and developers who want to understand what the hub is and what it can do before wiring anything up.
1. What the Hub Is
The Event & Data Hub is a platform service that aggregates events from across LIKE MAGIC and makes them available to systems outside the platform. It sits between the operational parts of LIKE MAGIC (reservations, folios, doors, tasks, messaging, configuration) and whatever you want to connect them to (a partner platform, an automation, a data warehouse, a dashboard).
Treat the event catalogue in this article as the current picture rather than a fixed contract. Confirm the exact events available to your account before you build against them.
2. Events, Not Just Records
A traditional integration reads records: it asks the API for the current state of a reservation, a folio or a task. The Event & Data Hub adds events: a notification that something happened, a reservation was created, a folio was updated, a door open succeeded, a task was completed.
Events are useful because they carry timing and intent:
- You learn when something changed, not just that it is now different.
- You can react the moment it happens: trigger a message, update an external system, or kick off a workflow.
- You avoid constantly polling for changes that may never come.
3. What You Can Do With It
The hub supports two broad patterns:
- Outbound webhooks: subscribe an external endpoint to a chosen set of events and have LIKE MAGIC deliver each one to that endpoint as an HTTP call. This is the operator-facing feature documented in Webhooks & Events.
- Analytics and data-out: stream property activity (bookings, reservations, folios, tasks, messaging) into reporting, business-intelligence or data-warehouse tooling so it can be analysed alongside the rest of your data.
Both patterns read from the same underlying event stream; webhooks are simply the delivery mechanism you configure yourself in the Operations Platform.
4. The Event Catalogue
Events are grouped by the area of the platform they come from. The main families are:
| Area | Example events |
|---|---|
| Booking (IBE) | booking succeeded / failed, booking created / updated |
| Reservation | created, updated, checked in, checked out, cancelled, no-show, room upgrade, pre-check-in / pre-check-out flow progress |
| Folio & billing | folio created, folio updated |
| Doors & locks | door open success / failure, door-access sync, lock and gateway connection lost / restored |
| Units & profiles | unit created / updated, profile created / updated / merged, profile language updated |
| Tasks | task created, updated, completed |
| Messaging | conversation created / updated / resolved, message sent / received / failed |
| Notifications | reservation, booking and account notification sent / failed |
| Configuration & promo | account configuration updated, promo code created / updated / deleted / used |
You choose exactly which of these your subscription receives. See Webhooks & Events for how to pick topics.
5. How Access Is Controlled
Whether you can use the hub depends on your pricing tier, your role and, for some events, the property's PMS:
- Pricing. Webhook subscriptions require Platform pricing. On Core the webhook subscriptions page is shown locked with an upgrade prompt. See Pricing Tiers.
- Role. Webhook subscriptions are managed at account level. The Account Administrator role (
account-admin) can edit them, and Account Viewer (account-viewer) sees the page read-only. - PMS. Some events only exist where the connected property management system emits them (see the next section).
Because the hub can carry sensitive operational data outbound, treat access to it (and the service accounts and secrets that consume it) as security-sensitive.
6. PMS and Event Coverage
LIKE MAGIC supports the following PMSs:
- Apaleo
- Mews
- Oracle Opera Cloud via OHIP
Reservation, folio and booking events originate from the PMS integration, so the exact events a property emits, and their timing, depend on that property's PMS. Events that are internal to LIKE MAGIC (tasks, messaging, doors, configuration, promo codes) are not tied to the PMS in the same way. Always confirm event coverage against the specific property you are integrating.
7. Getting Started
- To subscribe an endpoint to events, follow Webhooks & Events.
- To let an external system authenticate to the API and read events, issue a scoped service account (the
event_log.readandmetric.readscopes cover event and metric access).
8. Conclusion
The Event & Data Hub is how LIKE MAGIC lets the outside world react to what happens inside your properties, in real time, rather than repeatedly asking what changed. Use it to drive automations through webhooks and to feed property activity into your analytics stack, scoped to exactly what each integration needs.