Webhook plan limits (max subscriptions, log retention) are enforced server-side. See Webhooks Overview for the full limits matrix and payload templating reference.
Every command below honors the global flags:
--json (default) or --table for output format, --verbose for extra logging, and --api-key <key> / --api-url <url> to override credentials (also configurable via the SOME_API_KEY and SOME_API_URL environment variables).webhooks:create
Create a new webhook subscription.Examples
webhooks:list
List all webhook subscriptions in the current workspace.Examples
webhooks:get
Fetch a single subscription by ID, including its current state and failure counters.Examples
webhooks:update
Update any field on an existing subscription. Only the fields you pass are modified.At least one field must be supplied or the command exits with an error.
--active and --inactive are mutually exclusive — passing both also errors out.Examples
webhooks:delete
Permanently remove a subscription. No further deliveries are attempted.Examples
webhooks:test
Queue a syntheticwebhook.test delivery to verify your endpoint is reachable and your signature verification works.
Examples
webhooks:deliveries
List recent delivery attempts (both successes and failures) with pagination.Examples
webhooks:retry
Re-queue a previously failed delivery. Uses the original subscription, event, and payload.Examples
webhooks:events
List every event name the API supports, grouped by category. Useful for building--events filters or validating your subscription configuration. The response is an array of { category, label, events } objects.
Examples
Payloads & signature verification
See example payloads for every event category and learn how to verify the
X-Webhook-Signature header.