A webhook is a way for an app to get instant notifications from other applications. Webhooks are automated messages (also called payloads) sent to a specific URL. Unlike a classic call to an API, webhooks are more efficient than just polling it.
Webhooks help integrate Bump into your current workflows. The chosen URLs will receive an HTTP request automatically when Bump notices a structural change in your documentation.
Notifications can be sent to several URLs, allowing better integration with your existing tools.
Select the Integrations tab from your Bump’s dashboard to reach the webhook section.
After adding your webhook, a confirmation will be displayed. From this screen, you can modify the payload URL and find the secret token to be used (which helps to secure requests coming from Bump).
Here is a pseudo-code (in Ruby language) which you should implement in your server if you want to check the authenticity of the received payload:
signature = "sha256=" + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new("sha256"), ENV["SECRET_TOKEN"], payload_body)
return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env["HTTP_X_BUMP_SIGNATURE_256"])
The Recent deliveries section include a Test Webhook element that helps you verify that the webhook works correctly. You can also check the 10 last notifications.
Details about the payload content sent for each setup webhooks is available in our absolutely gorgeous API documentation.
Delete a webhook
To stop receiving notifications, you can delete a webhook by selecting it from the Integrations section and then confirm the deletion in the Danger zone.