Webhooks best practices
As a technical user, you use webhooks to set up or integrate applications and get real-time updates whenever an event or action occurs. The admin of a Zoho Sign account can configure a webhook and choose the events that will trigger it.
The callbacks may occasionally fail for varying reasons, such as incorrect URL configurations and server load issues on the client side. This puts a considerable load on our servers.
To avoid repeated callback failures, we recommend that admins follow these best practices:
- Whenever an admin configures a webhook to get real-time updates of actions that occur in Zoho Sign, our servers must receive a HTTP 200 response within 5 seconds to consider it a successful callback.
- Before returning the webhook callback, it is advisable not to do heavy processing with the webhook data available.
- Ensure that the configured webhook URL is always valid and accessible.
In case of repeated callback failures, admins will receive the following system-generated emails:
Warning threshold email: After 10 to 15 consecutive callback failures, an alert email will be sent from our system automatically.
Webhook disabled email: Once the callback failures reach the threshold limit of 20 consecutive callback fails, the system will automatically disable the webhook, preventing further callbacks to the same URL.The admin should identify the cause of failure and re-enable the disabled webhook from Zoho Sign web interface.
For any further queries or assistance, feel free to write to us at support@zohosign.com (for non-EU residents) and support@zohosign.eu (for EU residents).