The delivery API is powered by a CDN network consisting of hundreds of servers distributed across continents. The CDN layer is purged when you publish an entry in a space. Purging is instantaneous and the fresh content propagtes within seconds. However, there is throttling logic that slows down cache purging if you publish a space programatically (e.g. every few seconds).
If you depend on fresh data in a webhook target which triggers for publish, its usually best to implement a small polling script to ensure the data you get from the CDN is fresh.
Following is a snippet to implement a polling script:
The webhook system is hosted in AWS us-east-1 region.
The IP ranges for AWS are provided in the following link:
For committed customers we guarantee sending webhooks exclusively from the following list of IPs:
Changes to this list will be communicated three months upfront through your customer success manager.
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.
When creating a new webhook, the URL field will reject:
Private IPs (10.x, 192.x, etc.)
Hostnames without a Top Level Domain
URLs that resolve to localhost or redirects
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:
entity ID e.g.
environment ID e.g.
content type ID e.g.
sys.contentType.sys.id (for entries only)
For more information see: Webhook filters.
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.