--- created: 2025-03-10T10:10 updated: 2025-03-12T16:47 author: Florian Klein title: Webhooks --- # Webhooks ## Usage Use webhooks to notify your system about certain events within ibelsa. ## Info ### Event The following events are currently supported: | **Event** | **Description** | **Parameters** | |---------------------------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `MAINRESERVATION_CREATED` | Triggers when a mainreservation is created. | <li>`id` => id of the mainreservation</li> | | `MAINRESERVATION_UPDATED` | Triggers when a mainreservation is updated. | <li>`id` => id of the mainreservation</li> | | `MAINRESERVATION_REMOVED` | Triggers when a mainreservation is removed. | <li>`id` => id of the mainreservation</li> | | `ROOMRESERVATION_CREATED` | Triggers when a roomreservation is created. | <li>`id` => id of the roomreservation</li> <br><li>`mainres_id` => id of the related mainreservation</li><br><li>`is_modification` => if creation is part of a channelmanager modify</li> | | `ROOMRESERVATION_UPDATED` | Triggers when a roomreservation is updated. | <li>`id` => id of the roomreservation</li> <br><li>`mainres_id` => id of the related mainreservation </li> | | `ROOMRESERVATION_REMOVED` | Triggers when a roomreservation is removed. | <li>`id` => id of the roomreservation</li> <br><li>`mainres_id` => id of the related mainreservation</li><br><li>`is_modification` => if creation is part of a channelmanager modify</li> | | `CONTACT_CREATED` | Triggers when a contact is created. | <li>`id` => id of the contact</li> | | `CONTACT_UPDATED` | Triggers when a contact is updated. | <li>`id` => id of the contact</li><br><li>`is_deleted` => 1 if the update is a deletion. </li> | | `CONTACT_REMOVED` | Triggers when a contact is removed. | <li>`id` => id of the contact </li> | | `ROOMSTATUS_UPDATED` | Triggers when a roomstatus (dirty/clean) is updated. | <li>`id` => if of the room</li><br><li>`is_clean` => `true` / `false`</li> | #### Channelmanager modifications Channelmanager modifications are processed by ibelsa as deletion and creation of new room reservations. This also means that these modifications trigger webhooks of the types `ROOMRESERVATION_REMOVED` and `ROOMRESERVATION_CREATED`. In order to recognize these, the webhooks receive an additional parameter in these cases. ### Request Methods ibelsa Webhooks currently only support GET-Requests. ### Authentication Each webhook can be provided with its own basic authentication. ## Managing Webhooks via the API Even if it is possible for hoteliers to store webhooks manually, it is recommended that partners store webhooks automatically via API during onboarding. ### Adding a Webhook [Add Webhook](/api/doc#post--api-webhook-add) ### List Webhooks [List Webhooks](/api/doc#get--api-webhook-list) ### Updating a Webhook [Update Webhook](/api/doc#post--api-webhook-edit-{uuid}) ### Removing a Webhook [Remove Webhook](/api/doc#post--api-webhook-remove-{uuid}) # Migration from API Push Notifications to Webhooks Webhooks were previously known as “API Push Notifications”. The configuration was also less extensive. All “API Push Notifications” were migrated automatically and continue to work without the need for adjustments by the partner. In addition, the old API Push Notification endpoint is still compatible with webhooks. However, it is recommended to switch to the new webhook endpoints. Deprecated API Push Notification Documentation: [API Push Notification](/doc/api/push_notifications)

Author: Florian Klein 2025-03-10T10:10 2025-03-12T16:47

This page was generated from a Markdown file.

Would you like to view the content in your favourite Markdown reader? Raw Markdown