project.webhook_configured

Sent immediately after you set or replace a project’s webhook URL from the Notifications tab (or the equivalent API call) — delivered to the URL and signed with the secret you were just shown, as a confirmation ping.

Tip

Use this as your first real signal that a new webhook configuration works: if your endpoint receives it and the signature verifies, your setup is correct before you depend on it for anything else.

Headers

Header	Description
X-Baiyar-Signature	t=<unix timestamp>,v1=<hex HMAC-SHA256> — see Verifying Webhook Signatures
Content-Type	application/json

Payload

{
  "id": "evt_TmwUkYbLQ2sVn7RdWX34",
  "type": "project.webhook_configured",
  "created_at": "2026-09-16T04:03:46Z",
  "data": {
    "id": "project_IChAi2NR4vzKN3SgEYPI",
    "webhook_url": "https://merchant.example.com/webhooks"
  }
}

Field	Type	Description
id	string	Unique event ID
type	string	Always project.webhook_configured
created_at	date-time	When the event was generated
data.id	string	The project’s public ID
data.webhook_url	string	The URL just configured — always matches where this event was delivered

Replacing an existing URL always issues a fresh secret too (see Configure a Webhook) — this event fires for that case as well, signed with the new secret.

Testing

Trigger it by setting or replacing a sandbox project’s webhook URL from the dashboard — no separate simulator needed, since this event fires as a direct result of that action.

Next steps

project.webhook_removed — fires when a webhook is disconnected instead.