The Webhooks API is in beta. While the API is in beta, Snyk may change the API and the structure of webhook payloads at any time, without notice. During this beta, Webhooks are available only in the Snyk US-01, US-02, EU-01, and AU-01 regions.
Webhooks allow you to be notified of Snyk system events, enabling you to build notifications and react to changes in your projects. The current implementation supports events for recurring scans of open source and container image related projects.
When events are triggered, Snyk sends HTTP POST requests to URLs you have configured for those events, with all the information you need.
Receive instant notifications/alerts in your organization's business communication/collaboration software.
Respond to critical issues before they impact your business. Embrace modern incident management and Snyk to stay ahead of application security. Read more about this use case in the blog "Shifting left security incident management with the Snyk & Opsgenie integration".
Get real-time security alerts aggregated across various sources into a single platform. Read more about Snyk's partnership with Rapid7 and how together we help organizations mitigate security risks.
Browse the various Snyk Partner integrations for a comprehensive list of solutions.
Webhooks can only be configured for URLs using the HTTPS protocol. HTTP is not allowed.
When creating a webhook, you must provide a secret - this is a string that only you know that we will use to sign our transports to you so that you can ensure they come from Snyk. Your secret should be:
A random string with high entropy
Not be used for anything else
Only known to Snyk and your webhook transport consuming code
All transports sent to your webhooks will have a X-Hub-Signature header, which contains the hash signature for the transport. The signature is a HMAC hexdigest of the request body, generated using sha256 and your secret as the HMAC key.
X-Hub-Signature always starts with sha256=
Last updated
Was this helpful?
Was this helpful?
