Configure a Webhook

Set the URL

1. In the dashboard, open a project and go to its Notifications tab.
2. Enter your callback URL — it must be https://, enforced server-side — and save.
3. Copy the signing secret shown. Like an API key’s secret, it’s shown once — store it alongside the code that verifies incoming webhooks.

Caution

Setting or replacing the URL always issues a fresh secret, so there’s never a URL pointing at a stale, still-active one. If you rotate the URL, update your handler with the new secret at the same time.

Sandbox and production are configured separately

The Notifications tab is scoped to whichever environment is selected in the dashboard’s top bar — sandbox and production each get their own callback URL and signing secret, not a shared one. Configuring a webhook while in Sandbox does nothing for Production, and vice versa; switch environments and repeat the steps above to enable webhooks for both.

Tip

Easy to miss when going live: your sandbox webhook working doesn’t mean production is set up too. Configure it separately — see Go Live.

Removing a webhook

Remove webhook in the same Notifications tab disconnects the URL entirely — Baiyar stops sending events, and the project shows as having no webhook configured until you set one up again.

Next steps

Once you have a URL and a secret, go to Verifying Webhook Signatures to confirm requests are genuinely from Baiyar before you trust them.