Webhooks allow you to react to important events in your project by sending HTTP POST requests to a URL you specify.
For example, you can use webhooks to:
To register a webhook:
Every webhook request sent by Kobble will be signed with a secret key.
It’s crucial to validate the signature of the request to ensure that it was sent by Kobble and not by a malicious user.
To validate the signature, you need to compare the signature sent in the Kobble-Signature
header with the signature of the request body.
The signature is a HMAC-SHA256 hash of the request body using the secret key as the key.
You can get your secret key in the webhook detail page.
To validate the signature, you need to compare the signature sent in the Kobble-Signature
header with the signature of the request body.
Here is an example of how to validate the signature in Node.js and Python:
Kobble will always send the following headers with a webhook request:
The easiest way to test a webhook is to use the Send ping event button located in the webhook detail page.
Then, you can check the result on the latest deliveries section.
Kobble will retry sending the webhook request up to 5 times if the server responds with a 5xx status code or if the request times out.
The retry policy is exponential, starting with a delay of 10 seconds and doubling the delay for each retry.
If the webhook request fails after 5 retries, Kobble will stop sending the request and mark the webhook as failed.
Kobble will send the webhook request as soon as possible after the event occurs.
The delivery behavior is defined as “at least once”, meaning that Kobble will try to deliver the webhook request at least once.
In rare cases, the webhook request may be delivered more than once due to network issues or race conditions.
To handle this, you should make your webhook endpoint idempotent, meaning that it should be safe to call the endpoint multiple times with the same data.
Webhooks allow you to react to important events in your project by sending HTTP POST requests to a URL you specify.
For example, you can use webhooks to:
To register a webhook:
Every webhook request sent by Kobble will be signed with a secret key.
It’s crucial to validate the signature of the request to ensure that it was sent by Kobble and not by a malicious user.
To validate the signature, you need to compare the signature sent in the Kobble-Signature
header with the signature of the request body.
The signature is a HMAC-SHA256 hash of the request body using the secret key as the key.
You can get your secret key in the webhook detail page.
To validate the signature, you need to compare the signature sent in the Kobble-Signature
header with the signature of the request body.
Here is an example of how to validate the signature in Node.js and Python:
Kobble will always send the following headers with a webhook request:
The easiest way to test a webhook is to use the Send ping event button located in the webhook detail page.
Then, you can check the result on the latest deliveries section.
Kobble will retry sending the webhook request up to 5 times if the server responds with a 5xx status code or if the request times out.
The retry policy is exponential, starting with a delay of 10 seconds and doubling the delay for each retry.
If the webhook request fails after 5 retries, Kobble will stop sending the request and mark the webhook as failed.
Kobble will send the webhook request as soon as possible after the event occurs.
The delivery behavior is defined as “at least once”, meaning that Kobble will try to deliver the webhook request at least once.
In rare cases, the webhook request may be delivered more than once due to network issues or race conditions.
To handle this, you should make your webhook endpoint idempotent, meaning that it should be safe to call the endpoint multiple times with the same data.