Clerk webhooks notify your application about authentication events, including user sign-ups, sign-ins, profile updates, and organization changes. They are essential for syncing user data with your backend database.
Clerk webhooks are HTTP POST requests that Clerk sends to your server when specific events occur in your account. Rather than continuously polling the Clerk API for updates, webhooks deliver real-time notifications the moment something happens — a payment completes, a user signs up, a deployment finishes, or any other tracked event.
Debugging these webhooks can be challenging because they originate from Clerk's servers, not your browser. You can't simply open DevTools to inspect them. That's where WebhookVault comes in — capture every Clerk webhook, inspect the full payload and headers, and replay them to your local development server.
| Event | Description |
|---|---|
| user.created | Fired when a new user signs up |
| user.updated | Fired when a user's profile information changes |
| session.created | Fired when a user signs in and a new session is created |
| organization.created | Fired when a new organization is created |
Follow these steps to start capturing and debugging Clerk webhooks using WebhookVault.
Sign up for a free WebhookVault API key and create an endpoint to capture Clerk webhooks.
curl -X POST https://webhookvault.anethoth.com/api/v1/endpoints \
-H "Authorization: Bearer wv_your_key" \
-H "Content-Type: application/json" \
-d '{"name": "Clerk Webhooks"}'
# Response:
# {"url": "https://webhookvault.anethoth.com/hook/abc123", "inspect_url": "https://webhookvault.anethoth.com/inspect/abc123"}Go to the Clerk Dashboard > Webhooks Click 'Add Endpoint' and enter your WebhookVault URL Select the events you want to subscribe to (user.created, session.created, etc.) Save and copy the signing secret for webhook verification
Once Clerk sends a webhook, you can inspect every detail through the WebhookVault API or web inspector.
curl https://webhookvault.anethoth.com/api/v1/endpoints/abc123/requests \
-H "Authorization: Bearer wv_your_key"
# Returns all captured Clerk webhook requests with full headers, body, and metadataReplay any captured Clerk webhook to your local development server for testing.
curl -X POST https://webhookvault.anethoth.com/api/v1/endpoints/abc123/requests/1/replay \
-H "Authorization: Bearer wv_your_key" \
-H "Content-Type: application/json" \
-d '{"url": "http://localhost:3000/webhook"}'
# The original Clerk webhook is replayed to your local serverHere is an example of a typical Clerk webhook payload. Use WebhookVault to capture real payloads from your Clerk account for accurate testing.
{
"type": "user.created",
"object": "event",
"data": {
"id": "user_2abc123",
"object": "user",
"email_addresses": [
{
"email_address": "[email protected]",
"verification": {
"status": "verified"
}
}
],
"first_name": "Jane",
"last_name": "Doe",
"created_at": 1706000000,
"updated_at": 1706000000
}
}Here are the most common issues developers encounter when working with Clerk webhooks, and how to resolve them.
Clerk uses Svix for webhook delivery. Verify the svix-id, svix-timestamp, and svix-signature headers using Clerk's webhook secret.
user.created webhooks may arrive before your frontend redirect completes. Handle race conditions with retry logic.
Clerk development and production instances have separate webhook configurations. Test with your development instance first.
User payloads include all metadata and email addresses. Large custom metadata can result in oversized payloads.
Clerk webhooks are HTTP callbacks that Clerk sends to your server when specific events occur. Instead of polling the Clerk API for changes, webhooks push real-time notifications to your application, making your integration more efficient and responsive.
Use WebhookVault to capture Clerk webhooks in the cloud, then replay them to your localhost. Create a WebhookVault endpoint, configure Clerk to send webhooks to it, and use the replay API to forward captured requests to http://localhost:3000/webhook (or your local port).
Most webhook providers, including Clerk, sign their webhook payloads to prove authenticity. Check the Clerk documentation for the specific signature header and verification algorithm. Use WebhookVault to capture and inspect the raw headers to debug signature verification issues.
Unlike ngrok, WebhookVault captures and stores every webhook request with full headers and payloads. You can replay any Clerk webhook to your local server as many times as needed, inspect historical requests, and share webhook data with your team. No tunnel to maintain or port to expose.
Create a free WebhookVault endpoint in seconds. Capture, inspect, and replay Clerk webhooks with zero configuration.
Get Free API Key