(TO THE GOD OF ABRAHAM, ISAAC AND JACOB. I DEDICATE THIS WORK TO YOU MAY YOU BLESS IT AND MAY IT BLESS THOSE YOU USE IT, MORESO MAY THEY KNOW YOU BY NAME, REPENT AND BE LED TO YOUR WILL AND KINGDOM.) Our Father who is in the heavens, let Your Name be set-apart,let Your reign come, let Your desire be done on earth as it is in heaven. Give us today our daily bread. And forgive us our debts, as we for- give our debtors. And do not lead us into trial, but deliver us from the wicked one because Yours is the reign and the power and the esteem, forever. Amen.
ThunderHooks - Webhook Testing & Debugging Tool | Test Webhooks Locally

Endpoints

Creating webhook URLs and configuring mock responses

What's an endpoint?

An endpoint is a permanent URL that captures incoming HTTP requests. Each endpoint has a unique slug, so your webhook URL looks like:

https://thunderhooks.com/h/{slug}

All HTTP methods work — POST, GET, PUT, PATCH, DELETE, and anything else your provider sends.

Creating endpoints

From the dashboard, click New Endpoint and enter a name. ThunderHooks generates a random slug, but you can customize it if you want something memorable.

Mock responses

By default, endpoints return a 200 OK with an empty body. You can customize this to simulate your real API:

  1. Open the endpoint and click Settings
  2. Enable Mock Response
  3. Set the status code (e.g. 201)
  4. Add a response body
{
  "status": "received",
  "id": "mock-12345"
}

This is useful when the webhook provider expects a specific response format or status code to confirm delivery.

Request history

Every request is stored and available in the endpoint detail view. You can see:

  • The 50 most recent requests
  • Full headers, body, and query params for each
  • Timestamp and source IP

Replaying requests

Click Replay on any captured request to re-send it to an arbitrary URL. This is handy for:

  • Debugging a handler that failed on the original delivery
  • Testing retries against your local development server
  • Reproducing issues in a staging environment

Real-time updates

The endpoint detail page uses server-sent events (SSE) to show new requests as they arrive. No need to refresh — incoming webhooks appear instantly.