Introduction
SolidHooks receives inbound webhooks, verifies them, stores them as a system of record and delivers them to your services with retries.
SolidHooks sits between the services that send you webhooks and the services that act on them. A provider such as Stripe or GitHub posts to a SolidHooks URL instead of your server. SolidHooks checks the signature, stores the request exactly as it arrived, and delivers it to every destination that should see it, retrying until each one acknowledges it.
Nothing is lost along the way. Every request is stored before it is delivered, including the ones that fail verification, so you can always answer "did that webhook arrive, and what happened to it?"
Start here
Quickstart
Create a source, point it at a destination and watch your first delivery land.
How SolidHooks works
The pipeline from provider to destination, and the objects along the way.
The pipeline
provider → source (verified) → event stored → connections matched → deliveries → destination- A source is an inbound endpoint with its own URL. It knows how its provider signs requests.
- A destination is an HTTP endpoint you own: a public URL, or a service inside a private network.
- A connection routes a source to a destination, optionally filtered by event type.
- An event is one stored inbound request.
- A delivery is one event sent to one destination, with its full attempt history.
Go deeper
Receiving
Verify signatures, deduplicate retries from the provider, and receive email as events.
Delivering
Retries, signing what your endpoint receives, throughput, and delivery into private networks.
Operating
Replay and retry during an incident, tail activity live, and rotate secrets without downtime.
Access
API keys, Agent Auth, plans and usage, and every error code.
Built for people and agents
Everything the dashboard does is also an HTTP API call. AI agents can hold their own delegated identity instead of a shared key.