What is a Webhook?

A Webhook automatically sends data to an external server whenever an event occurs inside the system. Unlike polling an API (repeatedly calling it to check for changes), a Webhook only sends a notification when an event actually happens, so it uses fewer resources and enables near-real-time integration.

With Re:Earth CMS Webhook, whenever an item or asset in a project is edited, deleted, published, or otherwise changed, a real-time notification is sent to an external service. This makes it easy to integrate with external systems, automate workflows, and keep data in sync.

• Notifications for item creation, updates, and deletion
• Notifications when an item’s publication status changes
• Real-time notification via an HTTP POST to a specified URL
• A signature attached to each request so you can verify it hasn’t been tampered with

If you want to retrieve or operate on CMS data from the outside, use Integration API or Public API instead.

Here are a Webhook’s key characteristics.

Characteristic	Description
A mechanism for CMS event notifications	When an event such as item creation, update, deletion, or publication occurs, the CMS sends an HTTP POST request to a specified URL.
Configured under an Integration	A Webhook can’t exist on its own — you can add multiple Webhooks to a single Integration.
Signature verification required	Each request carries a signature generated from a secret. The receiving side must verify it to prevent spoofing.

Caution

To use Webhook, you need to set up a receiving server ahead of time and implement signature-verification logic. Building and operating the receiving server requires application-development knowledge and experience.

Next steps

Start with Creating an Integration — it’s a prerequisite for setting up a Webhook.

Related resources

• Getting started: Using Webhook — setup steps and event types