Skip to main content
Every wbhk command accepts the global flags: --output (text or json), --api-url, --color / --no-color, and --profile. Add --output json to any read command for a machine-readable view. Run wbhk <command> --help for the live surface.

Auth and session

Endpoints

An endpoint is a webhook.co URL that captures inbound requests. create and rotate reveal the ingest URL; it’s shown then and stays viewable in your dashboard and via endpoints reveal. delete, rotate, and revoke-provider-secret prompt for confirmation in an interactive terminal, or take --yes; non-interactively without --yes they refuse. --kind is signing_secret (default) or verify_token (a Meta hub.verify_token handshake token). Dedup modes are validated at the CLI before the request.

Events

List filters:

Deliveries

Outbound deliveries — auto-deliveries to subscribed destinations, plus manual replay attempts. --status filters by queued, pending, delivered, failed, dead, blocked, or forwarded (repeatable / comma-separated). --destination and --subscription filter to one id.

Listen

Stream an endpoint’s events live over a signed tunnel, or forward each one to localhost. In an interactive terminal this opens a browsable replay TUI; piped, it’s a plain line tail (--output json gives NDJSON). See replay to localhost.

Replay

Re-deliver a captured event, either to your machine or to a registered destination.

Replay destinations

The org’s allowlist of remote HTTPS URLs a server-side replay may deliver to. Referencing a destination by id — never a free-form URL — is a deliberate safety control. See send to a destination.

Subscriptions

Routing rules that auto-deliver a source endpoint’s captured events to a destination. --provider limits routing to one provider (default: any). --event-type selects event-type patterns — exact, charge.*, or * — repeatable or comma-separated (default *). --require-verified routes only events whose source was authenticated — the verified and authenticated states — excluding unattempted and failed.

Triggers

Webhook-to-agent trigger subscriptions: register to be woken when an endpoint captures an event, then consume those events. A trigger creates no outbound delivery — it only lets you consume events you can already read. For wait: --cursor resumes from a prior call’s nextCursor; --limit caps events (1–200); --no-body skips the inline body for a cheaper poll; --max-body-bytes caps each inline body (1–65536).

Usage, audit, maintenance