PMS webhooks for hotels
Send events out. Take events in. Signed both ways.
Send a property’s events to your own system as signed HTTPS posts, or receive signed events from it. Developers set both up in the App store.
What it does
- Choose the events to send from a searchable list. New event types are never added to a subscription by themselves.
- Each post is signed with your secret, so your system can check it came from LobbyMind.
- Timeouts, 429 and 5xx answers are retried. A 4xx answer is not.
- The inbound webhook takes signed JSON, ignores a repeated event id and maps fields by JSON path.
What syncs, and which way
| Data | Direction |
|---|---|
| The property events you select | Out of LobbyMind |
| Signed events from your own system | Into LobbyMind |
Set it up
Open the App store and choose Custom webhook, or Custom inbound webhook.
For outbound, enter your endpoint URL, choose events from the list and set a signing secret.
For inbound, set a signing secret and the JSON paths of the event type and id, then give your system the connection’s address.
Send the test event, then check the run history.
A few things you might be wondering.
How do we check that a post came from LobbyMind?
Each post carries a signature made with your signing secret. Compute it again from the body and compare.
What happens when our endpoint is down?
Timeouts, 429 and 5xx answers are retried. A 4xx answer is not, and a request over 64 KB is not sent.
Can our system send events in?
Yes. The inbound webhook accepts signed JSON and turns each accepted post into an event the property’s apps can process.
Let’s talk about your property
More clarity for your team. More care for your guests.
See how LobbyMind could fit your day, your property and your next chapter.
Book a demo