Receive Webhooks Locally
wajub listen forwards your webhooks to localhost — test your handlers without deploying or setting up a third-party tunnel.
6 min read
Testing webhooks locally is painful: your localhost is not reachable from the internet.
wajub listen solves this by forwarding your account's events directly to your
machine.
POST
/webhooks (forwarded → localhost)Start listening
wajub listen --forward-to localhost:3000/webhooks
# ✓ Ready — events forwarded to localhost:3000/webhooks
# › Session signing secret: whsec_cli_3f9a...
# 2026-05-24 10:21:09 payment.succeeded evt.7Yh2MpQ → 200Dedicated signing secret
In listen mode, the CLI signs with a session secret (whsec_cli_…) displayed at startup.
Use it in your local verification rather than your production secret. See
Signature verification.
Filter events
Only forward what interests you:
wajub listen --forward-to localhost:3000/webhooks \
--events payment.succeeded,payment.failed,transfer.succeededTypical development loop
- Start your local server (
localhost:3000). - In another tab:
wajub listen --forward-to localhost:3000/webhooks. - In a third:
wajub trigger payment.succeeded(see Triggers). - Watch your handler receive the signed event, locally, instantly.