Inbound Webhooks

The Problem

You use Stripe for payments, GitHub for code, Shopify for orders. Each sends webhooks in different formats, with different signature schemes. You need a separate handler for each one.

How Inbound Webhooks Work

HookSniff acts as a proxy: external providers send webhooks to HookSniff, HookSniff normalizes them and delivers to your endpoint with a consistent format and signature.

1. Create an inbound config for the provider
2. Give the provider HookSniff's inbound URL
3. Provider sends webhooks to HookSniff
4. HookSniff normalizes and forwards to your endpoint

Create Inbound Config

curl -X POST https://hooksniff-api-1046140057667.europe-west1.run.app/v1/inbound \
  -H "Authorization: Bearer hr_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{\"provider\": \"stripe\", \"endpoint_id\": \"ep_abc123\"}'

Response includes the inbound URL to give to Stripe:

{
  "id": "inb_xyz789",
  "provider": "stripe",
  "inbound_url": "https://hooksniff-api-...run.app/v1/inbound/stripe/inb_xyz789",
  "endpoint_id": "ep_abc123"
}

Supported Providers

Benefits

• ✅ One endpoint — Receive from all providers through a single URL
• ✅ Consistent format — All webhooks delivered in the same format
• ✅ Unified monitoring — See all inbound webhooks in one dashboard
• ✅ Automatic retries — Failed deliveries are retried like any other webhook
• ✅ Signature verification — Provider signatures verified before forwarding