Skip to main content
For event-driven integrations — Slack notifications, downstream pipelines, status dashboards — webhooks are the right tool.

Configuring a webhook

In Settings → Webhooks:
  • URL — your endpoint
  • Events — which events fire (build complete, build failed, etc.)
  • Active — enable / disable without deleting
You can register multiple webhooks per org. Each fires independently.

What gets sent

Webhooks POST a JSON envelope to your URL:
The type field tells you which event fired. Common ones:

Verifying signatures

The request includes an X-BuildPixel-Signature header — an HMAC of the body using your webhook signing secret. Verify before trusting:
The signing secret is generated when you create the webhook and shown in the Settings UI.

Retries

If your endpoint returns non-2xx, BuildPixel retries with exponential backoff for a few attempts before giving up. Failed deliveries are visible in the dashboard’s webhook delivery log.

Common patterns