Listen to webhooks

Coming soon

Outbound webhooks are in active development and not yet available. This page describes the planned design so you can prepare. The full reference (event list, signature verification, retry policy, and code samples) ships with the feature. Follow the changelog for the release.

What webhooks will do

Today, integration is one direction: you push data into Noticia. Webhooks add the reverse path. Noticia will POST a signed payload to an endpoint you register whenever a subscribed event occurs, so your CRM stays current without polling.

The first use case is consent flowing back: when a customer replies STOP or is unsubscribed inside Noticia, your CRM is notified so its records match. The opt-out you honor in Noticia propagates to your source of truth.

Planned design

• Registration: declare an endpoint URL, a signing secret, and the events you subscribe to.
• Signature: each request will be signed with HMAC-SHA256 over the payload, carried in a Noticia-Signature header that includes a timestamp. You verify the signature and reject requests whose timestamp is too old, which prevents replay.
• Retries: failed deliveries will be retried with exponential back-off, with a dashboard to inspect and redeliver.
• Secret rotation: a previous signing secret stays valid for an overlap window so you can rotate without dropping events.

Prepare now

While you wait, design your receiver to be idempotent: a webhook may be delivered more than once, so deduplicate on the event id and make handling safe to repeat. That single habit makes adopting webhooks on day one straightforward.