Webhooks

Customer-facing outbound webhooks are not available today. You can't yet subscribe to events like "backup completed" or "Brand Monitor hit detected" from your own backend. The capability is on the roadmap; reach out via app.norcube.com to register interest.

What works today

Norcube uses webhooks internally and for two integrations:

Stripe inbound

Stripe sends events to Norcube's billing service – payment_method.attached, charge.succeeded, charge.failed, etc. – at POST /billing/webhooks/stripe. This is what drives dunning state transitions.

You don't need to do anything with this. It exists between Stripe and Norcube; it's not a webhook you can subscribe to.

Backup job webhooks (internal)

Backup workers POST job-completion events back to the Backup control plane. Internal-only; not exposed to customers.

Brand Monitor email alerts

Brand Monitor emails notifications when a watcher matches. Email isn't a webhook, but it's the notification surface for this product today.

What's planned

Customer-subscribable webhooks across products:

Backup – backup.completed, backup.failed.
LangSync – sync.completed, translation.added.
DomainRadar – bulk_check.completed, watcher.hit (replacing email).

Expected shape:

Per-org webhook endpoints registered via the dashboard.
Per-event subscription filtering.
HMAC-SHA256 signatures over the payload (X-Norcube-Signature).
At-least-once delivery with retry on non-2xx response.

No timeline yet. We'll publish design RFCs ahead of shipping.

In the meantime

Polling is the workaround:

For Backup, query GET /datasources/{id}/backups periodically and watch the status field.
For LangSync sync jobs, poll GET /namespaces/{name}/sync/{id}.
For DomainRadar bulk checks, use the Server-Sent Events stream – not exactly a webhook, but real-time without polling.

Billing → Dunning – Stripe inbound webhooks in action.
DomainRadar → Configure alert emails – the current alert channel for Brand Monitor.