Webhooks

Each webhook will be a POST request with a JSON body containing information about the status of your websites. You can use webhooks when monitoring reachability, broken links, mixed content, or the execution of cron jobs.

How to add a webhook

You can start receiving webhook notifications using the steps in this section:

1. Create a webhook endpoint: Create a webhook endpoint (URL) that can accept POST requests with JSON data.
2. Enter the webhook URL: Go to the Notification settings in Semonto. Select the test for which you want to activate a webhook and scroll down to the Webhooks section. Enter your webhook endpoint URL in the dashboard and save your entry.
3. Test the webhook: Once created, you can send a test message.

How to interpret the webhook data

You can expect the webhook to return data in the following format.

Webhook data for reachability notifications

• The ID of the monitor
• The type of test results: in this case, ‘reachability’.
• The status as a string in which 0 = OK, 1 = warning, 2= critic, and 3 > error.
• The name of the monitor.
• The test date.
• The tested URL.
• And for each test, the name, status and test info.

This is an example of what that could look like:

TLS/SSL notifications

The webhook data for TLS/SSL certificate notifications contain the following data:

• The name of the monitor.
• The status as an integer and as a string. 0 means OK, 1 means warning, 2 means critical, and 3 or higher means error.
• The time the test was performed.
• The tested URL.
• The expiry date for the certificate as a UNIX timestamp.
• The number of days the certificate remains valid.
• Whether the certificate has expired.
• Whether the certificate expires soon.
• Any other errors encountered while validating the certificate.

This is an example of what that could look like:

Broken links and mixed content notifications

These are the webhook data you can expect to receive for broken links and mixed content notifications:

• The name of the monitor
• The status as an integer and as a string. 0 means OK, and 1 means warning, broken links or mixed content found.
• The time the test was performed.
• The tested URL.
• The number of broken links/cases of mixed content and the number of broken links/cases of mixed content found in the previous test run.

Here is an example set of data:

PulseCheck notifications

PulseChecks is our internal name for Cron Job Monitoring. The data for PulseCheck notifications contains:

• The name of the PulseCheck.
• The status as an integer and as a string. 0 means OK, and 3 means expired.
• The interval in seconds.
• The URL to call from your script.
• If the PulseCheck expired, how long it has expired in seconds.
• The timestamp of the last pulse with the IP address.

This is an example of what the returned data could look like:

Need any help?

Don’t hesitate to reach out to our team if you need any help setting up your webhooks. We are happy to help!