Webhooks

Webhooks notify an outside system when something happens in a project - an entry is created or published, for example - instead of that system having to poll the Content API for changes.

Delivery channels

A webhook delivers to either an HTTP URL (a POST request with the event payload as its body) or by email, to one or more recipients - useful for a team that wants a notification without standing up an endpoint to receive one.

Scoping a webhook

Choose which event types a webhook subscribes to, and optionally scope it to a single collection rather than the whole project - useful when only one team's content matters to a given integration.

Testing and delivery history

Send a test event on demand to confirm an endpoint (or email address) is reachable before relying on it, and review the delivery history for a webhook to see recent attempts and their outcomes.