Run & terminal
Webhook links and the request log
Give your running app a public URL for test webhooks from GitHub, Cashfree, Stripe and others — then see every request, its headers and body, and replay it.
Testing a webhook usually means a tunnel tool. KODEO has one built in.
Make a webhook link
In the Preview, press Share, switch on Webhook, enter the path your app listens on (for example /api/webhooks) and press Create webhook URL. Paste the URL into the service's webhook settings.
- It answers only under that path — everything else on your app stays private.
- No sign-in and no notice page: services can call it directly.
- Pro and Team (a Team policy can turn webhook links off).
From your computer: kodeo share 8080 --webhook /api/webhooks. From VS Code: KODEO: Share Port with KODEO… → Webhook URL.
The request log
Open the inspector (the bug button) → Requests. Every request that came in through your link is there — method, path, status, time, and who sent it (a teammate's name, guest or webhook).
Click one to see its headers and body (JSON is formatted). Then:
- Replay sends the same request to your app again — straight to your runtime, not through the internet.
- Edit & replay lets you change the method, the path or the body first.
What's kept
The log lives only in your browser tab, for this session — KODEO's servers never store requests or bodies. Headers that carry secrets (authorization, cookies, signatures) and JSON fields like password or token are hidden before anything is kept, so a replay leaves them out too.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?