Skip to main content
When a webhook delivery fails, Hookdrop can analyze the error and tell you what went wrong — and what to do about it.
AI features require Starter plan or above. Upgrade your plan to get access.

​
Use it from the dashboard

Click any failed event in your dashboard, then select Diagnose with AI. Hookdrop reviews the delivery attempts, response codes, and response bodies, then returns a specific explanation and suggested fix.

​
Use it from the API

GET /api/endpoints/:id/events/:eventId/ai/diagnose
Authorization: Bearer YOUR_API_TOKEN

​
Example response

{
  "diagnosis": "Your server returned a 401 Unauthorized response, which means the request signature check failed. Verify that your HMAC secret matches the one configured in your provider's dashboard, and that you're reading the raw request body — not the parsed JSON — when computing the hash."
}

​
What the AI diagnoses

The diagnosis is based on your server’s response code and body from each failed delivery attempt. Common causes it identifies include:
  • Wrong URL — the endpoint path doesn’t exist or has a typo
  • Non-2xx response — your server returned an error code like 400, 401, 404, or 500
  • Timeout — your server took too long to respond and the delivery was abandoned
  • SSL issues — your server’s TLS certificate is invalid, expired, or self-signed
  • Authentication errors — signature verification failed due to a mismatched secret or incorrect body parsing
Diagnosis accuracy depends on the information your server returns. If your server returns a generic error body like {"error": "something went wrong"}, the AI has less to work with. Return descriptive error messages from your handler to get more actionable diagnoses.