...
Webhooks allow you to build or set up integrations with GeoSeeq, such as apps , which that subscribe to certain GeoSeeq events on GeoSeeq. When one of those events is triggered, we'll send a an HTTP POST payload to the webhook's configured URL. The following properties can be set for a webhook.
Webhook
...
URL
The target urlURL, where payload payloads are sent when preconfigured events occureoccur.
Webhook secret
Once your server is configured to receive payloads from GeoSeeq, it will listen for any payload sent when preconfigured events occureoccur. For security reasons, you probably want to should limit requests to those coming from GeoSeeq. There are a few ways to go about do this (for example, you could opt to allow requests from GeoseeqGeoSeeq's IP address), but a far easier method is to set up a secret token and validate the information. When your secret token is set, GeoSeeq uses it to create GeoSeeq creates a hash signature with each payload when your secret token is set. This hash signature is included with the headers of each request as X-SignitureSignature-SHA256. The intention is to calculate a hash using your secret token , and ensure that the result matches the hash from GeoSeeq. GeoSeeq uses an HMAC hex digest to compute the hash.
...
You have the option to configure the SSL verification settings. If your webhook url URL is not secure (HTTP), this option won't have anny any effect. By default, GeoSeeq verifies the SSL certificate of your website when delivering webhook payloads. SSL verification helps ensure that hook payloads are securely delivered to your URL endpoint securely. You have the option to can disable SSL, but we recommend keeping Enable SSL verification selected.