Webhooks
Register webhook endpoints to receive real-time event notifications from Clevername. Subscribe to specific events, test payloads, and monitor delivery status.
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 is created, drift is detected, or a review submission is approved.
Available events
Events are tiered; higher plans inherit the lower tiers.
- Free —
skill.published,skill.installed,mcp.installed,webhook.test - Pro adds —
mcp.disconnected,agent.created,agent.status_changed,agent.drift_detected,agent.auto_restricted - Team adds —
review.submitted,review.approved,review.rejected,approval.requested,approval.resolved,org.member_added,org.member_removed - Enterprise adds —
scan.blocked,key.health_failed,baseline.locked
Leaving the event list empty subscribes the endpoint to every event your plan allows. Endpoint caps are also per plan: 1 on Free, 5 on Pro, 25 on Team, unlimited on Enterprise.
Delivery and retries
Each delivery is attempted up to 3 times in total (1 initial attempt plus 2 retries) with short backoff of 1 second, then 4 seconds. An attempt fails if your endpoint does not return a 2xx status code within 10 seconds. 5xx responses, 429, timeouts, and connection errors are retried; any other 4xx response is treated as a rejected payload and is not retried. After 10 consecutive failed deliveries the endpoint is disabled automatically; re-enable it from the dashboard once your receiver is fixed.
Open Webhook settings
Go to Settings → Webhooks in the dashboard (this tab is shown on Team and higher). On Free and Pro, open /dashboard/webhooks directly. You will see a list of registered endpoints or an empty state.
Add a webhook endpoint
Click Add Webhook. Enter a name, the URL of your endpoint (must be HTTPS), and a signing secret of at least 16 characters that you generate yourself. Select the events you want to subscribe to, or leave them all unchecked to receive every event your plan allows.
Store the signing secret
The signing secret is the value you supplied at registration — Clevername does not generate one for you. Store it securely on your server and use it to verify that incoming webhook payloads are genuinely from Clevername.
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.
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.