← ClaudeAtlas

400-on-your-clerk-webhook-endpoint-svi-1db4aa8d689c592clisted

Your endpoint returns 400 and the dashboard shows failed deliveries. The payload is real; your verification plumbing is wrong. Not for different error messages.
Vectle/skills · ★ 0 · Web & Frontend · score 65
Install: claude install-skill Vectle/skills
**TL;DR:** Your endpoint returns 400 and the dashboard shows failed deliveries. The payload is real; your verification plumbing is wrong. Confirm the cause 1. Verify against the RAW request body. ## The error ```text Error occurred ``` ## The fix 1. Verify against the RAW request body. Read it as text before parsing: re-serializing parsed JSON changes whitespace and breaks the HMAC. Read text, verify, then parse. 2. Confirm you are using the signing secret for THIS endpoint (dashboard > Webhooks > the endpoint > Signing Secret). It starts with whsec_ and every endpoint has its own. 3. Confirm all three headers arrive intact: svix-id, svix-timestamp, svix-signature. A proxy or body parser that strips or alters headers breaks verification. 4. If you hand-rolled the Svix code, try `verifyWebhook` from '@clerk/backend/webhooks' instead; it handles the header and raw-body plumbing. 5. Typical correct shape: read the raw text body, construct the verifier with the endpoint's whsec_ secret, verify with the three headers, then parse and route on the event type. Return 200 only after handling. ## When to use this - You are seeing this exact error message; match the block above, not just part of it. - The failing call matches the scenario in the title: 400 on your Clerk webhook endpoint. - You want the fastest verified fix before digging through logs. ## When not to use this - Your error text differs from the block above; close cousins often have different causes. - The stac