Quick start
WebhookCore is service-first. The quickest path is to run the API, boot the dispatcher, and then send one endpoint plus one delivery through the example.
Prerequisites
Section titled “Prerequisites”- Node
24.x - pnpm
10.33.x - Docker with Postgres and Redis support
Local bootstrap
Section titled “Local bootstrap”cp .env.example .envdocker compose up -d postgres redispnpm installpnpm dev:apipnpm dev:dispatcherLocal surfaces:
- API:
http://localhost:3030 - Dispatcher health:
http://localhost:3031/health - Postgres:
localhost:5432 - Redis:
localhost:6379
First useful checks
Section titled “First useful checks”curl http://127.0.0.1:3030/healthcurl http://127.0.0.1:3030/readycurl http://127.0.0.1:3030/metricsFirst delivery flow
Section titled “First delivery flow”pnpm example:outbound-integrationThe example:
- registers one endpoint
- creates one delivery
- lists recent deliveries
- schedules a replay
What you should understand after 5 minutes
Section titled “What you should understand after 5 minutes”- WebhookCore wants delivery state explicit and auditable
- endpoint governance, secret rotation, and attempt history are first-class
- replay is part of the core model, not a support-only hack
- QueueFlow can own retry scheduling without becoming hidden magic