![Automate with webhooks](/_gatsby/image/b26f9d6fd334049e5618af05cd21d875/008158768e0040463898135da34bc4a3/felix-russell-saw-112140.jpg?u=https%3A%2F%2Fimages.ctfassets.net%2F1ove3zmijz58%2F4shwYI3POEGkw0Eg6kcyaQ%2F2a892ecf32c8b8a36a6f89d316ee95a0%2Ffelix-russell-saw-112140.jpg&a=w%3D750%26h%3D500%26fm%3Djpg%26q%3D75&cd=2024-07-09T15%3A36%3A07.494Z)
Automate with webhooks
Webhooks notify you, another person or system when resources have changed by calling a given HTTP endpoint.
What are webhooks?
The webhooks are used to notify you when content has been changed. Specify a URL, configure your webhook, and we will send an HTTP POST request whenever something happens to your content.
How do I configure a webhook?
Go to Settings → Webhooks from the navigation bar at the top. From there, hit Add webhook, and you will be directed to your new webhook. Then choose a name, put in the information of your HTTP endpoint (URL and authentication), specify any custom headers and select the types of events that should trigger the webhook.
Why do I get an old version in the CDA?
As the delivery API is powered by a CDN network consisting of hundreds of servers distributed across continents, it takes some time (up to a few minutes) to reflect the changes to the published content. This must be taken into consideration when reacting to webhooks. In normal conditions, there could be a reasonable delay of 2 to 5 minutes.
Extracted from the Webhooks FAQ.