Defining a webhook receiver endpoint

To receive webhooks from Ascenda, you need to define a publicly accessible webhook receiver endpoint on your platform. This endpoint is where Ascenda will configure to send webhook events. Refer to this guide on setting up the webhooks.

To ensure that your webhook receiver endpoint works correctly with Ascenda's platform, it must meet the following requirements:

The webhook receiver endpoint must use HTTPS. Ascenda will not publish webhooks to a non-HTTPS endpoint.
The webhook receiver endpoint must return a response with a 200 HTTP status code. This lets Ascenda know that your platform has successfully received the webhook. The payload in the response body is not used by Ascenda.
The webhook receiver endpoint must provide a response within 10 seconds. If complex processing is required, it should be done asynchronously only after a response (200 OK) has been provided back to Ascenda.

If the webhook receiver endpoint does not respond with a 200 OK status code, or if there is no response after 10 seconds, Ascenda's platform will retry sending the webhook up to a total of 5 times, with an increasing exponential back-off waiting time for each retry. If all retry attempts fail, the webhook will be marked as failed, and an email notification will be sent to your defined email address with information about the failed webhooks.