Set up webhooks
Webhooks in resmio are a streamlined trigger method to notify external services in real time about changes to reservations and online orders.
General
Simply put, webhooks enable resmio to connect to third-party applications and automatically notify them of specific events.
Examples of such events include confirmed reservations or orders.
A webhook is an automated notification sent via HTTP request, which resmio sends to a URL you have specified as soon as a specific event occurs.
The following use cases are feasible:
- Event-driven workflows (a system should respond to certain events without knowing the details)
- Internal notifications (you/the team should be informed that something has happened)
- Counts and status synchronization (third-party application simply counts events)
- Monitoring and technical processes
Common applications for resmio webhooks include automation platforms such as Zapier, Make, or n8n, internal servers, notification services (Slack, Teams), or reporting tools like Google Sheets, which respond to events without processing reservation or order data.
| Point | Description |
|---|---|
| Method | HTTP POST |
| Authentication | Basic Auth |
| Format | JSON |
| Payload | id, facility_id, action |
| Purpose | Trigger for external applications |
| Details | API needed |
You can easily set up and update webhooks directly through your resmio account..
- Log in to the system and go to
Settings > Integration > Developers > Webhooks - Add a new webhook by clicking the + Add webhook button.
- The following info needs to be provided for the webhook:
- a target URL for the HTTP request
- a username (for authorization)
- the password (for authorization)
- the desired action/event
Settings > Integration > Once your webhook is saved in resmio, we’ll automatically send an HTTP POST request to your URL when the selected action happens. Your app will then get the request and can respond accordingly (like saving data, starting a specific process, etc.).
Authentication is performed via Basic Auth (username & password). This data is sent in the HTTP header. Your server checks the credentials before processing.
There are currently a total of six webhook actions available in resmio.
| Area | Trigger | Meaning |
|---|---|---|
| Reservations (booking) | booking_created | A new reservation has been created. |
| Reservations (booking) | booking_updated | An existing reservation has been changed (e.g., time, number of people). |
| Reservations (booking) | booking_deleted | A reservation has been canceled or deleted. |
| Online orders (productorder) | productorder_created | A new online order has been received. |
| Online orders (productorder) | productorder_updated | An existing order has been modified. |
| Online orders (productorder) | productorder_deleted | An order has been canceled or deleted. |
The webhook request currently contains only a minimal payload.
A practical example:
{
"id": 51918313,
"facility_id": "the-fish",
"action": "BOOKING_CREATED"
}
The fields included are:
id
The internal ID of the reservation or order assigned by resmio.
facility_id
The unique identifier of the resmio account (restaurant).
action
The triggered event, all webhook actions, see table above.
Webhooks are primarily used as triggers, not for full data processing.
