HookHound

Troubleshooting webhook monitoring

If HookHound isn't detecting events or schema changes, the webhook usually never reached your endpoint — or the event didn't differ from the previous schema. Use the steps below to diagnose the issue quickly.

1. Send a test event

Use the "Send test event" button on the integration page first.

If the event appears in Recent Events, HookHound is working correctly.

If the HookHound test event succeeds but your provider webhook does not, the problem is usually in the provider webhook configuration rather than in HookHound.

2. Verify the webhook endpoint

Make sure the webhook URL configured in your provider exactly matches the endpoint shown in HookHound.

Common mistakes:

  • Using the wrong endpoint
  • Missing the ingress key
  • Using a staging URL instead of the production endpoint
  • Copying an outdated endpoint

Example endpoint format:

https://your-hookhound-domain/in/abc123

3. Confirm your provider is sending events

Check your provider's webhook delivery logs and confirm that webhook deliveries are being sent successfully.

  • Stripe: Developers → Webhooks → Event deliveries
  • GitHub: Repository Settings → Webhooks → Recent deliveries
  • Shopify: Settings → Notifications → Webhooks

If the provider is not showing successful webhook deliveries, HookHound will not receive anything to process.

4. Test the endpoint with curl

Verify the endpoint independently using curl. Replace the URL with your actual webhook endpoint:

curl -X POST https://your-hookhound-domain/in/abc123 \
  -H "Content-Type: application/json" \
  -d '{"event":"test"}'

If this request appears in Recent Events, the endpoint is working.

If the curl request works but your provider's events do not, the provider configuration is the likely issue.

5. Why alerts may not trigger

HookHound only sends alerts when a breaking schema change is detected.

Alerts may not trigger when:

  • Events are received but the schema has not changed
  • The schema changed in a non-breaking way
  • Alerts are not configured for the integration
  • The current plan does not support the selected alert channel

6. How schema changes are detected

HookHound creates an initial schema version from the first event it receives for an integration.

When later events have a different structure, HookHound compares them to the latest known schema.

If the structure changes: a new schema version is created, a schema diff is recorded, and breaking changes can trigger alerts.

This means HookHound needs at least one valid event before it can begin comparing future payloads.

Common issues

  • No events received yet
  • Webhook URL is incorrect
  • Provider webhook is disabled
  • Wrong environment is being used
  • Events were sent before the integration was configured
  • Alert channels are not configured
  • Email alerts are unavailable on the current plan

Next steps