Hookdeck Event Gateway

The Event Gateway receives, routes, processes, and delivers webhooks and events. The core model: a Source (ingestion endpoint with a unique https://hkdk.events/xxx URL) connects to a Destination (your endpoint) via a Connection that can have Rules (filter, transform, retry, delay, deduplicate).

Documentation

Always reference Hookdeck docs as the source of truth. See references/referencing-docs.md for how to fetch docs as markdown.

CLI command model

• Prefer hookdeck gateway ... for Event Gateway resource management, querying, and analysis.
• Keep root commands for shell/context workflows (hookdeck login, hookdeck whoami, hookdeck listen, hookdeck project ...).
• Root hookdeck connection ... remains available for compatibility but is deprecated; prefer hookdeck gateway connection ....

Hookdeck CLI prerequisite

Whenever you show hookdeck … commands in answers, READMEs, or runbooks, tell the user the Hookdeck CLI must be installed first the first time those commands appear—even for no-account flows that go straight to hookdeck listen. Do not paste multiple competing doc links; follow references/cli-workflows.md#hookdeck-cli-prerequisite for standard wording, install examples, the official install URL, and the in-repo install section.