Documentation
Learn how to use hooksnode for reliable webhook delivery at any scale.
Quickstart
Send your first webhook through hooksnode in under a minute. No SDK required — just an HTTP client.
1. Create an account
Sign up at hooksnode.com/register and create a project. You'll get a unique inbound URL.
2. Send a webhook
Point any HTTP client at your inbound URL:
curl -X POST https://hooksnode.com/in/acme \
-H "Content-Type: application/json" \
-d '{"event":"payment.succeeded","amount":5000}'3. Add a destination
Configure where the webhook should be forwarded — your API, a Slack webhook, or any HTTP endpoint.
4. Monitor in real time
Watch events arrive in the dashboard. Inspect payloads, check delivery status, and replay failed events.
How Webhook Delivery Works
Webhook Ingestion
Send a POST request to your project's proxy URL. hooksnode persists the payload to the database before queueing — ensuring zero webhook loss even if Redis is temporarily unavailable. Every event returns a 202 Accepted immediately.
Include an Idempotency-Key header to prevent duplicate deliveries when retrying the same inbound request.
Fan-Out Delivery
One inbound webhook fans out to multiple destinations, each with its own queue, retry policy, and delivery log. Destinations are processed concurrently so one slow endpoint never blocks others.
Automatic Retries
Failed deliveries retry with exponential back-off. On the final attempt, an alert is sent to the project owner. You can also manually re-enqueue any failed event from the dashboard.
Filter Rules
Configure per-destination JSON filter rules to forward only matching events. Filters use flat key-value matching against the inbound payload. Non-matching events are dropped silently.
Payload Transformation
Reshape outbound payloads per destination using Go text/templates. Wrap payloads in envelopes, restructure fields, or add metadata before forwarding.
HMAC Signing
When you enable signing on a destination, every forwarded request to it carries an X-Hooksnode-Signature: sha256=... header your endpoint can verify. Signatures are HMAC-SHA256 of the raw request body using that destination's signing secret. Signing is opt-in per destination — it's off by default.
Use Cases
Real-world scenarios where hooksnode's webhook multiplexing solves infrastructure problems.
Payment Webhook Routing
Your payment processor (Stripe, Flutterwave, Paystack) sends one webhook per event. You need that event in your accounting system, your CRM, your analytics pipeline, and your notification service. Instead of building a custom fan-out for each processor, point all payment webhooks to hooksnode and configure each downstream system as a destination. Add per-destination filter rules so invoices go to accounting and chargebacks go to fraud detection.
Multi-Channel Alerting
Your monitoring system fires an alert webhook when a server goes down. You need Slack notified, PagerDuty paged, an email sent to the on-call engineer, and the event logged to your incident management system. hooksnode fans out the alert to every channel simultaneously — each with its own retry policy so a Slack rate-limit never silences your PagerDuty notification.
Event-Driven Microservices
You're migrating from a monolith to microservices and need to broadcast domain events (order placed, user registered, payment received) to multiple services. hooksnode acts as your event router — each microservice registers as a destination and receives only the events it needs via filter rules. Payload transformation lets you reshape events per service without coupling them to a shared schema.
Webhook Debugging & Inspection
Third-party APIs send webhooks and you have no visibility into what they're actually delivering. Route all inbound webhooks through hooksnode first: inspect the full payload and headers in the live event inspector, verify HMAC signatures before forwarding, and replay any event to test your integration. Once you're confident, add your production destination — hooksnode logs every delivery attempt so you always have an audit trail.
Third-Party Integration Distribution
Your SaaS platform lets users connect third-party services via webhooks. Instead of each user configuring webhooks individually from each provider, give them a hooksnode inbound URL. Webhooks arrive at a single endpoint and are fanned out to each connected integration. Users get a unified event log and can replay failed deliveries without contacting each provider's support.
Data Pipeline Ingestion
Your platform emits webhook events for every significant action. You want those events in your data warehouse for analytics, in your search index for real-time search, and in your audit log for compliance. Point the event stream at hooksnode and configure each data system as a destination. Use payload transformation to format events appropriately for each sink — JSON for the warehouse, flattened fields for the search index.
API Reference
hooksnode provides two API surfaces:
- REST API (v1) — Programmatic access with API key authentication (
Authorization: Bearer mplx_...). List projects, events, and retry deliveries. - Browser API — Session-authenticated endpoints for the SPA dashboard. Manage projects, destinations, billing, and settings.