webhooks test suite
翻译准备中
正在加载完整 README。
查看完整 README ↗Use the live demo: create an endpoint and point any service at its URL. Nothing to install.
A local install is for trying testhooks out. Services on the internet can't reach localhost, so it only receives requests you send from your own machine, for example with curl.
curl -fsSL https://raw.githubusercontent.com/sarathsp06/testhooks/main/install.sh | sh && testhooks
Or with Docker:
docker run --rm -p 8080:8080 ghcr.io/sarathsp06/testhooks
Open http://localhost:8080. Data is kept in memory and is gone when it stops.
To receive real webhooks, run testhooks somewhere the sender can reach, with PostgreSQL:
AUTH_TOKEN and ALLOWED_ORIGINS; see Production.localhost and sends your app's reply back to the sender, so you can test your handler without ngrok. Nothing to install.testhooks endpoints create, testhooks requests wait, testhooks requests send: the command line does what the UI does and prints JSON when piped.testhooks mcp lets Claude Code or Cursor create an endpoint, wait for the provider's request, preview a script on it and write your handler from real traffic. A SKILL.md teaches the workflow, the API describes itself at /api/openapi.json, and READ_TOKEN gives an agent a token that can only read.The docs cover configuration, the API and how each mode works.
Needs Go 1.26+ and Node 22+.
make build && ./testhooks # build the binary with the UI embedded
make dev # API on :8080 and Vite with hot reload
make test # Go tests
See CONTRIBUTING.md.
The code is under the Apache License 2.0: use it, change it, self-host it, for anything.
The name "Testhooks" and the logo are trademarks and are not covered by the code license. Forks need their own name, and offering a hosted service under the Testhooks name needs permission. See TRADEMARKS.md.