Receive webhooks on a local app

You are wiring up webhooks from a payment provider, a git host, or a chat platform, and they need to POST to a public HTTPS URL. But your handler runs on localhost where the provider cannot reach it. Point a Kepeink tunnel at your handler and paste the assigned hostname into the provider's webhook settings — deliveries land on your local app in real time, so you can watch and debug them as they arrive.

Why Kepeink is great for this

• The provider gets a stable public HTTPS URL; your handler stays on your machine.
• You see each delivery hit your code immediately — no redeploy loop to test a change.
• Attach a custom domain if the provider requires a fixed, branded callback URL.

The recipe

1. Run your webhook handler locally, for example on port 4000:

   node webhook-server.js
   # → listening on http://localhost:4000/hooks

2. Create a proxy tunnel targeting http://localhost:4000 and copy its agent token.
3. Run the agent (foreground is fine while you are testing):

   curl -fsSL https://cdn.kepeink.hu/run.sh | sh -s -- --token=kpt_xxxxxxxx

4. In the provider's dashboard, set the webhook URL to your assigned hostname plus your handler's path, for example https://<your-host>/hooks.
5. Trigger an event and watch it arrive in your local logs. Inbound POSTs travel down the tunnel to http://localhost:4000 and your handler responds.

Because Kepeink only relays traffic, the request bodies, headers, and signatures your handler needs arrive intact for verification.