Syntax and options for `uip or webhooks`, which manages Orchestrator HTTP callbacks fired on platform events.

Manage Orchestrator webhooks — HTTP callbacks fired on platform events (job completion, queue-item failure, and so on). Webhooks are tenant-scoped.

For the cross-resource conventions (auth, key types, output envelope), see the uip or overview.

List webhooks. Filters: -n, --name, --enabled, --disabled (mutually exclusive). --sort-by <field> sorts results (default Id desc); --all-fields returns the full API response.

Get webhook details by key, including subscribed events and SSL settings. --all-fields returns the full API response.

Create a webhook. Requires <name> and --url. Optional -d, --description, --events <comma-list> (omit to subscribe to all event types), --secret, --allow-insecure-ssl.

Update by key. Providing --events switches the webhook from subscribe-to-all to the given list. Pass --enabled or --disabled to toggle the webhook's state (mutually exclusive).

Delete a webhook by key. Requires -y, --yes — the CLI never prompts for destructive operations.

Send a test ping to the webhook URL to verify connectivity. Delivery is asynchronous — a successful response means the ping was queued, not that the endpoint received it; confirm receipt on the endpoint itself.

List every event type a webhook can subscribe to. Use the returned names with create --events or update --events.

See Exit codes for the shared contract. delete exits 1 if -y, --yes is omitted.