Webhooks
Webhooks let BCTRL notify your server when automation changes state. Create an HTTPS endpoint, subscribe it to event types, and process each delivery after verifying its signature.
Create an endpoint
The URL must use HTTPS and cannot contain embedded credentials. name is optional. events must contain at least one event type.
The create response includes the signing secret. Store it securely. get() and list() return the endpoint configuration but never return the secret again.
Event types
A delivery body is a webhook envelope:
Verify the delivery signature with the secret before using data. Keep the raw request body available to your verification code; do not parse and reserialize it before verification. The SDK manages webhook endpoints and delivery records; your HTTP server is responsible for receiving and verifying incoming requests.
Manage an endpoint
Update any combination of name, url, events, and enabled. Deleting an endpoint does not remove its historical delivery records.
Webhook fields
Rotate the signing secret
Rotation replaces the current secret immediately. The new secret is returned only in the rotation response.
Update your receiver to use the new secret before rotating in production, or be prepared for deliveries signed with the new secret immediately after rotation.
Test and troubleshoot deliveries
Send a signed test event and inspect the resulting delivery record:
When the receiver is fixed, queue another attempt for a failed delivery:
Delivery fields
Next
- Runs — inspect the automation events that webhooks reference
- Views — create live or replayable automation views
- Account and organization — scope endpoints and manage API keys

