Test Loops webhooks
Loops sends webhooks for contact and mailing list changes, email sends, and delivery, bounce, open, click, unsubscribe, and spam complaint events. Capture them on a free webhooks.cc endpoint to see exactly what Loops sends, then replay deliveries or forward them to your local handler.
No credit card · 50 requests/day free · or get a guest URL without an account
Prefer a walkthrough? Read the local webhook testing guide.
How to test Loops webhooks
- 1
Create a webhook endpoint
Sign in free with GitHub, Google, or email to create a persistent endpoint, or grab an instant guest URL at webhooks.cc without an account.
- 2
Point Loops at your URL
Paste the endpoint URL into Loops: Settings → Webhooks.
- 3
Inspect what arrives
Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.
- 4
Forward to localhost or assert in CI
Run whk tunnel <port> to forward webhooks to a local server, or use the TypeScript, Python or Go SDK to wait for and assert on deliveries in tests.
Loops webhook authentication
| Auth header | webhook-signature |
|---|---|
| Algorithm | HMAC-SHA256 |
| Verification in webhooks.cc | Capture deliveries to inspect raw signature material |
The header holds space-separated v1,{base64} entries, each an HMAC of {webhook-id}.{webhook-timestamp}.{raw body} keyed with the signing secret minus its whsec_ prefix, base64-decoded. After a secret roll, both secrets sign for 24 hours.
New to signature verification? Read the webhook signature verification guide.
Everything in one place
- Live dashboard: see deliveries the moment they arrive
- Forward to localhost with whk tunnel
- Replay any captured request to any URL
- Mock responses with custom status, headers, and body
- Forward to your servers, Slack or Discord
- TypeScript, Python and Go SDKs for CI assertions
- MCP server for AI coding agents
Loops webhook questions
Create a free endpoint on webhooks.cc (sign in with GitHub, Google, or email, or use a guest endpoint without an account), then configure it as your webhook URL: Settings → Webhooks. Every delivery shows up live in the dashboard with full headers, body, and query parameters. To hit a local server, run whk tunnel <port> and the CLI forwards each webhook to localhost.
Yes. Capture one real delivery from Loops, then replay it to any URL from the dashboard, or run whk tunnel <port> to forward live deliveries to localhost. webhooks.cc has no built-in Loops sample templates, but the Send button posts any payload and headers you paste in.
Loops authenticates each delivery with the webhook-signature header (HMAC-SHA256). The header holds space-separated v1,{base64} entries, each an HMAC of {webhook-id}.{webhook-timestamp}.{raw body} keyed with the signing secret minus its whsec_ prefix, base64-decoded. After a secret roll, both secrets sign for 24 hours. Capture a real delivery on webhooks.cc to inspect the exact header value, then implement the check in your handler.
Yes. A free account gets you persistent endpoints, 50 requests per day, 7-day retention, and full CLI, SDK, and MCP access, with no credit card. You can also try a guest endpoint without an account: up to 25 requests for 12 hours.
More providers
Your Loops webhook URL is seconds away
Sign up free, create an endpoint, and point Loops at it.
No credit card · or try without an account