Documentation
HookHound monitors webhook payloads, detects schema changes over time, and alerts you when integrations may break — or when webhooks stop firing.
What HookHound does
- Unique endpoint per integration — Each integration gets an HTTPS URL to receive webhooks from Stripe, GitHub, Shopify, or any provider.
- Schema extraction — Extracts the payload structure (shape) from incoming events and tracks it over time.
- Change detection — Compares schemas per event type and flags breaking changes (removed fields, type changes) vs non-breaking (added fields).
- Webhook silence monitoring — Detects when no events arrive within a configured threshold (e.g. misconfigured endpoint, provider outage).
- Alerts — Sends Slack and email notifications when breaking schema changes are detected or when webhooks go silent.
Quick links
- Quick Start — Create your first integration and send a test event.
- Understanding Schema Changes — How schema extraction, diffs, and breaking-change classification work.
- Webhook Testing — Test event button, curl, and real provider webhooks.
- Alerts — Slack and email configuration, when alerts trigger, plan requirements.
- Pricing and Limits — Plans, integration limits, event limits, schema history.
- Troubleshooting — Debug missing events, schema changes, or alerts.
Schema change detection and webhook silence monitoring
Third-party APIs change their webhook payloads over time. Fields get added, removed, or renamed. These changes can break your integration silently. HookHound captures each event, extracts its schema, and compares it to previous versions. When a breaking change is detected, you get notified before production errors occur.
HookHound also monitors for webhook silence — when no events arrive within a threshold you configure. That helps you catch misconfigured endpoints, provider outages, or revoked credentials before users notice.