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.
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. You can also specify filters for more fine control.
The webhook system is hosted in AWS us-east-1 region.
The IP ranges are provided in the following link:
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.
When creating a new webhook, the URL field will reject:
While creating your webhook, you will be asked to choose what type of events should trigger it. Events are separated by the type of entity (Content Type, Entry and Asset) and the underlying action (Create, Save, Autosave, etc). For example, you can create a webhook that will be triggered whenever an Entry is Unpublished.
For even more fine control have a look at webhook filters.
Yes, webhooks have a
filter property which can be used to filter webhooks based on properties of the entity that triggered the webhook. It is possible to filter on:
sys.contentType.sys.id(for entries only)
For more information see: Webhook filters.