Setup

The webhooks are "user-defined HTTP callbacks", usually trigged by specific events. When a certain event occurs, the source site makes an HTTP request to the URL configured for the webhook. Users can configure them to cause events on one site to invoke behavior on another.

Just to make an example, every time a new appointment is created, thanks to the webhooks you can notify a third-party URL with the details of the created reservation.

It is possible to manage the webhooks by visiting the Configuration > Applications page, where you should see a tab named Web Hooks.

Max Failure Attempts

The maximum number of sequential failures that every webhook can do. After reaching the specified amount, the webhook will be automatically unpublished.

The system registers a failure every time a webhook receives a response with an HTTP code equals or higher than 300. Take a look at this page to understand what are the supported HTTP status codes.

Register Logs

Enable this option to always track the responses received by the webhooks. The logs will be always saved within a .log file.

Group Logs

Here it is possible to choose how the logs should be grouped. Here's a list of supported values:

• Day - the logs will be saved in a file with a name built as YYYY-mm-dd.log;
• Week - the logs will be saved in a file with a name built as YYYY-W.log;
• Month - the logs will be saved in a file with a name built as YYYY-mm.log.

Logs Path

You can specify here the absolute path of the folder in which the logs will be stored.

It is strongly recommended to always use an unpredictable path to prevent unauthorized users to directly access your logs.

Manage Web Hooks

Click this button to access the management page of your webhook. Here you can see a list containing all the created webhooks and the tools to interact with them.