Webhookr
Webhookr is a developer-first platform for receiving, inspecting, replaying, and delivering webhooks.
Point any provider — Stripe, GitHub, Shopify, Typeform, or your own services — at a Webhookr endpoint. Webhookr captures every incoming request, stores the full payload and headers, and forwards it to the destinations you configure. When something goes wrong, you can inspect exactly what was received and replay it on demand.
Problems Webhookr solves
- No visibility into incoming webhooks. Providers send a request and move on. Webhookr keeps the full record — payload, headers, source IP, timing — so you can see exactly what arrived.
- Lost events during outages. If your service is down when a webhook arrives, the event is usually gone. Webhookr stores every event so you can replay it later.
- Painful local development. Testing webhooks against
localhostis awkward. Receive events in Webhookr, inspect them, and replay them into any environment. - One source, many consumers. A single incoming event often needs to reach several services. Webhookr fans each event out to multiple destinations and tracks every delivery independently.
- No infrastructure as code. Manage projects, endpoints, and destinations with the Terraform provider instead of clicking through a UI.
Core concepts
These terms are used consistently throughout the documentation.
| Concept | What it is |
|---|---|
| Project | A container for related endpoints. Usually one project per application or environment. |
| Endpoint | A public URL that receives webhook events. Identified by a unique slug. |
| Event | A single incoming HTTP request received by an endpoint, stored with its payload and headers. |
| Destination | A target URL where Webhookr forwards events received by an endpoint. |
| Delivery | One attempt to send an event to a destination. Has a status: PENDING, SUCCESS, or FAILED. |
| Replay | Re-sending a stored event to its destinations, or re-sending a single delivery. |
| Topology | A graph that visualizes how events flow: Source → Endpoint → Destination. |
| API Token | A whk_… token used to authenticate automation and the Terraform provider. |
The relationship between them:
Provider ──▶ Endpoint ──▶ Event ──▶ Destination(s) ──▶ Delivery
(Stripe…) (your slug) (stored) (your services) (per attempt)
A Project owns many endpoints. Each Endpoint receives many events and can forward to many destinations. Each Event produces one Delivery per enabled destination.
Where to go next
- Getting Started — the full onboarding path, from first endpoint to confirmed delivery.
- Fast Track — send your first webhook in a few minutes with
curl. - Concepts — deeper reference for each object.
- Terraform — manage Webhookr as code.