webhooks.lol

A small webhook endpoint for receiving and inspecting HTTP requests. The app creates unique receive URLs, captures requests sent to them, and shows the latest traffic in a compact inspector. It is intentionally simple: a request list, a detail pane, and a small remembered-endpoint switcher. Anonymous endpoints are disposable and browser-local. Signed-in endpoints are attached to the account that created them so they follow that account across browsers and sessions.

Quick Start

pnpm install
cp packages/database/.env.example packages/database/.env.local
cp apps/web/.env.example apps/web/.env.local
cp apps/docs/.env.example apps/docs/.env.local
cp apps/pgboss/.env.example apps/pgboss/.env.local
pnpm db:local:start
pnpm redis:local:start
pnpm db:migrate
pnpm dev

The development server runs on http://localhost:4665.

Each app/package reads environment variables from its own .env.local. The example files provide local defaults. Replace placeholder values as needed.

Local Services

pnpm db:local:start starts the local PostgreSQL Docker container, webhooks-lol-postgres. If the container does not exist, the script creates it with the webhooks-lol-postgres-data volume.

Equivalent manual creation command:

docker volume create webhooks-lol-postgres-data
docker run -d --name webhooks-lol-postgres \
  -e POSTGRES_DB=webhooks-lol \
  -e POSTGRES_USER=postgres \
  -e POSTGRES_PASSWORD=postgres \
  -p 5434:5432 \
  -v webhooks-lol-postgres-data:/var/lib/postgresql/data \
  postgres:18

pnpm redis:local:start starts the local Redis Docker container, webhooks-lol-redis. If the container does not exist, the script creates it with the webhooks-lol-redis-data volume.

Equivalent manual creation command:

docker volume create webhooks-lol-redis-data
docker run -d --name webhooks-lol-redis \
  -p 6379:6379 \
  -v webhooks-lol-redis-data:/data \
  redis:8 redis-server --appendonly yes

Usage

1. Open the app.
2. Optionally sign in or create an account before creating endpoints that should follow an account across browsers.
3. Optionally rename the current endpoint so it is easier to recognize later.
4. Copy the RECEIVE_URL.
5. Send any request to that URL, or to a nested path below it.

Example:

curl -X POST https://hooks.example.com/api/hook/<id>/events/created \
  -H "content-type: application/json" \
  -d '{"event":"created","id":"evt_123"}'

Captured requests appear live in the endpoint. Select a request to inspect the parsed body, headers, query string, and raw HTTP request.

CLI

The whlol CLI streams endpoint traffic from your terminal. Use it to forward captured requests to a local server, tail live requests, or replay stored requests. Forwarded and replayed requests preserve the original method, headers, and exact body bytes, so provider signature headers still verify locally.

The current CLI protocol supports anonymous endpoints only. Endpoints created while signed in are account-owned and require the owning browser session. Use anonymous endpoints with whlol until a dedicated CLI authentication or endpoint-token flow exists.

# Forward to a local server (creates an endpoint and prints its receive URL)
npx whlol forward --to http://localhost:3000/api/webhooks

# Stream live requests from an anonymous endpoint to the terminal
npx whlol tail <endpoint-id>

# Re-send a stored request from an anonymous endpoint
npx whlol replay <endpoint-id> --request <request-id> --to http://localhost:3000/hook

Point the CLI at a local or self-hosted deployment with --host http://localhost:4665 or the WEBHOOKS_LOL_URL environment variable. See apps/cli/README.md for command details and options.

Monorepo Structure

Path	Responsibility
apps/web	Primary Next.js application
apps/pgboss	Node.js PgBoss worker for endpoint forwarding
apps/cli	whlol command-line package
apps/docs	Fumadocs-powered Next.js documentation site
packages/database	Drizzle schema and PostgreSQL connection
packages/webhooks-core	Shared webhook types, IDs, search helpers, and API contracts
packages/webhooks-server	Server workflows, repositories, rate limits, replay, forwarding

Scripts

Use root commands for app and worker builds or verification so Turbo builds workspace package dependencies first.

pnpm dev               # start apps/web on port 4665
pnpm web:build         # production build for apps/web
pnpm web:verify        # typegen, typecheck, lint, test, and build apps/web
pnpm pgboss:dev        # run the PgBoss worker in development
pnpm pgboss:build      # build the worker and package dependencies
pnpm pgboss:start      # start the compiled PgBoss worker
pnpm pgboss:verify     # verify database/core/server packages and worker app
pnpm cli:verify        # verify the whlol CLI package
pnpm docs:start        # start the built docs app
pnpm docs:verify       # verify the docs app
pnpm db:generate       # generate Drizzle migrations in packages/database
pnpm db:local:start    # start local PostgreSQL with Docker
pnpm db:local:stop     # stop the local PostgreSQL container
pnpm db:local:logs     # follow local PostgreSQL logs
pnpm redis:local:start # start local Redis with Docker
pnpm redis:local:stop  # stop the local Redis container
pnpm redis:local:logs  # follow local Redis logs
pnpm db:migrate        # apply packages/database Drizzle migrations
pnpm db:push           # push schema directly for local prototyping
pnpm typecheck         # run TypeScript checks for every workspace package
pnpm build             # production build for apps/web
pnpm verify            # full workspace verification