My webhook endpoint keeps getting disabled due to various reasons, any best practices should I follow?

• Related Articles

• Best practices to follow for webhooks

  Keep the flexibility of retrieving unknown fields with the webhook response. As the platform evolves new fields are introduced time to time. Reading of webhook data should not fail while a new parameter is received. For example in Java you can use ...

• Will I be notified when my webhooks are disabled ?

  Yes, If the webhook endpoint is returning a non 200 response for more than 24 hours, webhook account is disabled and a Webhook disable email is sent to the registered email id. Sample email -

• For the period my webhooks were disabled, will I still be receiving the old webhook events or events created within this duration when my webhooks are enabled again?

  Yes, webhook events are queued and processed separately when webhook endpoint is working.

• How do I enable my webhooks back, if it's disabled due to non 200 responses for more than 24 hours?

  Once you fix the issue so that endpoint is returning 200, you can login to Enterprise dashboard and enable it back by pressing “Click to Activate” under webhook section. Refer below image -

• My endpoint is different for each type of webhook and only one type of event is throwing error, will other events also be stopped when webhooks are disabled?

  Yes, the queue is maintained at account level. While endpoints can be different but any failure impacts all types of events