Webhook Testing
Three ways to test your webhook endpoint:
1. HookHound test event button
On the integration page, use the Send test event button under "Test without your provider". This sends a minimal payload to your endpoint without configuring your provider. Useful for verifying the endpoint is reachable and receiving events.
2. curl command
The integration page includes a copyable curl command. Paste it into your terminal to send a test event from the command line:
curl -X POST https://your-domain.com/in/your-ingress-key \
-H "Content-Type: application/json" \
-d '{"event":"test","source":"hookhound-cli"}'Replace the URL with your actual webhook endpoint. The payload is minimal; HookHound will capture it and process it.
3. Real provider webhook
Configure your provider (Stripe, GitHub, Shopify, etc.) to send webhooks to your HookHound endpoint. Use the provider's webhook settings to add the URL and select the events you want to receive. For local development, use the provider's CLI (e.g. Stripe CLI) to forward events to your local server.
Verifying events
After sending an event, check the Recent Events section on the integration page. Events appear with processing status and schema change details when applicable.
Click an event to view its payload and headers. The event detail page includes a Copy as cURL button that generates a replay command. Infrastructure headers (x-forwarded-*, x-vercel-*, etc.) are excluded from the cURL output for cleaner replay.
Troubleshooting — If events or schema changes are not appearing, see the troubleshooting guide.