Create a webhook for a team
Registers a new webhook endpoint that will receive HTTP POST notifications for subscribed events. Returns the webhook ID and a signing secret.
Authorizations
User session JWT (Bearer ). Must be paired with the X-Team-ID
request header on team-scoped endpoints so the server knows which
team's resources to operate on.
Headers
UUID of the team to scope the request to. Used by dual-auth endpoints (runtime + scoped management):
- JWT callers MUST send it — a user may belong to multiple teams and the runtime cannot otherwise know which one to operate on. Missing header → 400.
- Credential callers (
sk-,dk-) can omit it because the team is derived from the credential row itself. Any value sent is ignored.
"019abc12-4567-7890-abcd-ef1234567891"
Body
Registers a webhook endpoint. The server signs each delivery payload with HMAC-SHA256 using a generated secret (returned in the webhook detail response).
Webhook Payload Format
Each delivery is an HTTP POST with JSON body:
Signature Verification
Each delivery includes an X-Webhook-Signature-256 header:
Verify by computing HMAC-SHA256(webhook_secret, raw_body) and comparing.
Retry Policy
Failed deliveries (non-2xx response or timeout) are retried up to 4 times with exponential backoff: immediate → 5s → 30s → 2min.
Human-readable name for the webhook.
1 - 255"Task Completion Notifier"
HTTPS endpoint URL to receive webhook payloads.
2048^https://"https://my-app.example.com/webhooks/cyberun"
List of event types to subscribe to:
task.completed: Fired when a task finishes successfully.task.failed: Fired when a task fails (including timeout and agent disconnect).
1task.completed, task.failed Response
Webhook created
UUID of the created or updated resource.
"019abc12-3456-7890-abcd-ef1234567890"
