How to test a webhook without a server

The quick answer: use a public endpoint that accepts any request and replies with what it received. Point your webhook at https://webhook.plus/anything/plus/my-test, trigger an event, and the response shows the exact method, headers, query and body that arrived. No server, tunnel or deploy needed.

Why test without a server?

When you're wiring up a new integration, the first questions are simple: does the sender fire at all, what does the payload look like, and which headers come with it? Answering those with your own code means building a route, deploying it somewhere public and adding logging. An echo endpoint answers them in a minute, before you've written any handler.

Step 1: pick an endpoint

Every path under /anything/ echoes, so make one up per integration. The home page generates a random one for you, or choose something descriptive:

https://webhook.plus/anything/plus/billing-test
https://webhook.plus/anything/plus/repo-push

Step 2: check it from your terminal

curl -X POST https://webhook.plus/anything/plus/billing-test \
  -H 'content-type: application/json' \
  -d '{"event":"invoice.paid","amount":1999}'

You'll get JSON back like this (trimmed):

{
  "method": "POST",
  "url": "https://webhook.plus/anything/plus/billing-test",
  "headers": { "content-type": "application/json", … },
  "data": "{\"event\":\"invoice.paid\",\"amount\":1999}",
  "json": { "event": "invoice.paid", "amount": 1999 },
  "args": {}, "form": {}, "files": {}
}

Step 3: point the real sender at it

Paste the URL into the provider's webhook settings, ideally in its test or sandbox mode, and send a test event. Most providers keep a delivery log that records the response they received. Because webhook.plus echoes the request, that log now shows the provider's own payload and headers side by side with the status code.

What can't an echo endpoint do?

  • It doesn't keep an inbox. The echo goes back to the sender; webhook.plus doesn't store a history for you to browse later.
  • It doesn't run your business logic. Once you know the payload shape, build your real handler.
  • It isn't private. Everything is recorded, so use sandbox data.

Next steps

Try different payload types in sending test webhooks with curl, or make the endpoint misbehave in testing retries.

Frequently asked questions

Do I need ngrok or a tunnel to test webhooks?

Not to see what a sender delivers. A public echo endpoint shows the payload and headers. You need a tunnel only when you want the webhook to reach code running on your own machine.