Receive Webhooks
Hookbase Inbound gives every webhook provider a stable endpoint to send to. Each incoming request is checked against the provider's signature, stored, and then routed to one or more destinations that you configure.
How It Works
Provider Hookbase Your Systems
┌──────────┐ POST ┌──────────────────────┐ deliver ┌──────────────┐
│ Stripe │ ────────▶ │ Source │ ──────────▶ │ API / Worker │
│ GitHub │ │ → verify signature │ │ Queue / DB │
│ Shopify │ │ → store event │ ──────────▶ │ Slack, S3 … │
└──────────┘ │ → route, filter, │ └──────────────┘
│ transform, retry │
└──────────────────────┘- Sources receive webhooks at
/ingest/:orgSlug/:sourceSlugand verify the provider's signature. - Routes connect a source to one or more destinations, with optional filters and transforms.
- Deliveries are retried automatically when a destination fails, and any event can be replayed later.
Where to Start
Quickstart
Create a source, a destination, and a route in a few minutes
Guide
Concepts and features: routes, filters, transforms, retries, replay
Provider Integrations
Setup steps and signature verification for each provider
API Reference
REST endpoints for sources, routes, events, and deliveries
CLI
Forward webhooks to localhost and manage resources from the terminal
MCP Server
Let AI agents inspect, debug, and replay your webhooks
Use Cases
End-to-end examples like Stripe fan-out and Shopify order routing
FAQ
Common questions about limits, retries, and security
Sending webhooks to your own customers instead? See Send Webhooks.