Skip to main content

Webhooks

Register webhook endpoints to receive real-time event notifications from Clevername. Subscribe to specific events, test payloads, and monitor delivery status.

Key Concepts

What are webhooks?

Webhooks send HTTP POST requests to your server when events happen in Clevername. Instead of polling the API for updates, your application receives real-time notifications as events occur — such as when an agent completes a task, an error is logged, or a review submission is approved.

Available events

  • agent.completed — an agent task finished successfully
  • agent.error — an agent task failed
  • council.approved — a review submission was approved
  • council.rejected — a review submission was rejected
  • budget.threshold — a scoped token budget reached its configured threshold
  • security.alert — a security event was detected

Delivery and retries

Clevername retries failed webhook deliveries up to 3 times with exponential backoff (30 seconds, 2 minutes, 10 minutes). A delivery is considered failed if your endpoint does not return a 2xx status code within 10 seconds.

Step-by-Step Guide
1

Open Webhook settings

Go to Settings → Webhooks in the dashboard. You will see a list of registered endpoints or an empty state.

Webhook settings page showing registered endpoints with status indicators and an Add Webhook button
The Webhooks tab shows all your registered endpoints and their delivery status.
2

Add a webhook endpoint

Click Add Webhook. Enter the URL of your endpoint (must be HTTPS). Select the events you want to subscribe to.

Add webhook dialog with URL field and event checkboxes
Enter your HTTPS endpoint URL and select which events to subscribe to.
Note
Webhook endpoints must use HTTPS. HTTP endpoints are rejected for security reasons.
3

Copy the signing secret

After creating the webhook, a signing secret is generated. Copy it and store it securely. Your server should use this secret to verify that incoming webhook payloads are genuinely from Clevername.

Important
The signing secret is shown only once. If you lose it, delete the webhook and create a new one.
4

Send a test payload

Click Test next to your webhook to send a sample payload. Check your server logs to confirm receipt. The test payload mirrors the real event format so you can validate your handler.

5

Monitor deliveries

Click on any webhook to see its delivery history. Each delivery shows the HTTP status code, response time, and payload sent. Failed deliveries show the error reason and retry schedule.