Skip to content
cascadehook.docs

Webhooks, delivered.

Everything you need to send signed webhooks, build a reliable receiver, and understand every delivery.

Cascadehook / Developer documentation

Cascadehook delivers your application's events to HTTPS endpoints. Publish an event once, route it by event type, and inspect the attempts made to each receiver.

How the pieces fit

  1. Your application publishes an event using a project API key.
  2. Cascadehook creates deliveries for enabled, subscribed endpoints.
  3. Your receiver verifies the signature and durably accepts the event.
  4. You inspect the result in the dashboard or through the API.

An event being accepted and a webhook being delivered are separate outcomes. An HTTP 202 confirms publication. A delivery marked succeeded confirms that the receiver acknowledged it.

Choose your next step

New to Cascadehook? Start with the quickstart. Already integrating? Read about events and idempotency, receiver signatures, and retries and replay.

For automated integrations, the agent protocol, Markdown guide, OpenAPI schema, and documentation index are available without signing in.

On this page