Hookman sits between your webhook provider and your deployments. Point Stripe (or Paddle, or GitHub, or anything) at one stable URL — Hookman routes it to whichever branch you're working on.
No credit card. 1,000 webhooks/month free.
You're deep in a PR for feature/checkout.
You need to test Stripe webhooks. So you do this:
Open the Stripe dashboard
Navigate to Developers → Webhooks. Find your dev endpoint.
Update the endpoint URL
Change it to your branch's preview URL. Remember the path. Paste it. Save.
Test your branch. Merge your PR.
Now you're on main. The endpoint still points to the dead preview URL.
Switch to a new branch. Repeat.
Every single time. For every webhook provider. For every developer on your team.
This isn't a Stripe problem. It's every webhook service. Paddle, GitHub, Shopify, Twilio — they all have the same model: one endpoint URL, configured once, expected to never change. Your branch deployments change constantly.
Set the Hookman URL in Stripe once. Then tell Hookman where each branch lives. Switch branches in your dashboard in one click — or let the GitHub Action do it automatically.
Seriously. Here's every step.
Sign up and create a project. Pick a slug — this becomes part of your Hookman endpoint. Your project maps to one webhook integration (e.g. your Stripe setup, or your GitHub webhooks).
Stripe
Paddle
GitHub
https://hookman.dev/w/your-org/your-project Tell Hookman where each branch lives. Use the dashboard, the CLI, or drop the GitHub Action into your workflow and let it handle registration automatically whenever a preview deploys.
HOOKMAN_API_KEY in your environment
and drop the --key flag entirely.
In Stripe (or wherever), update the webhook endpoint URL to your Hookman endpoint. You'll never need to change this URL again.
When you want to route webhooks to a different branch, flip the switch in the dashboard — or use the CLI. No Stripe dashboard. No copy-pasting URLs. The GitHub Action can do it automatically on every deployment.
The Hookman GitHub Action listens for deployment_status events —
which fire when Vercel, Netlify, or Cloudflare Pages post a preview URL back to GitHub.
It registers the deployment automatically, and removes it when the PR closes.
Works with any platform that posts deployment URLs back to GitHub — Vercel, Netlify, Cloudflare Pages, Render, Railway, and more. Full reference →
Every team works differently. Hookman supports three routing strategies — use one, or combine them.
Flip the active deployment in your dashboard or with
hookman switch. Webhooks follow.
Good for solo developers who control the flow.
Include a routing key in a custom header
(e.g. x-hookman-branch: feature/checkout)
and Hookman routes to the matching deployment automatically.
Point Hookman at a field in your webhook JSON body
(e.g. metadata.branch) and routing
happens based on whatever value the sender includes.
Hookman stores every webhook payload. Hit replay to re-deliver to any deployment — great for debugging without having to trigger a real payment or event again.
The GitHub Action registers and removes deployments automatically. Merge a PR? The deployment is cleaned up. No stale routes.
If your branch is spinning up, Hookman retries delivery with backoff rather than dropping the webhook. Available on Pro and Team.
No credit card to get started.
For solo devs and side projects.
For active teams shipping regularly.
For teams with multiple collaborators.
Get a Hookman endpoint in 60 seconds. Free to start, no card required.
Get your endpoint free