Changelog

Hookdeck CLI v3.2.0

Hookdeck CLI v3.2.0 returns event and request payloads from list commands, so you or your agent can read a batch of events in one call instead of fetching them one at a time.

Payloads in list commands. Add --include data to gateway event list, gateway request list or gateway request events, with --output json, and each result includes its headers, body, path and parsed query. With --include data, the limit defaults to 10 unless you pass --limit. In the Event Gateway MCP server, the list action of gateway_events_read and gateway_requests_read takes the same include argument.

hookdeck listen stops when Hookdeck rejects your credentials. When the connection is refused with a 401 or 403, or closed because your key was revoked, listen exits 1 and prints the server's message. It used to print Connection lost, reconnecting... and retry forever. Network drops and 503 responses still reconnect.

Connection rules run in the order you write them. On connection create, update and upsert, the position of each rule type's first --rule-* flag sets its position in the connection's rules. Before, rules were always built as deduplicate, transform, filter, delay, retry, so a filter written before a transform ran after it. --rule-transform-name now accepts a transformation's name or ID, and fails if neither exists.

Check your scripts. Some commands that exited 0 while ignoring part of your input now fail:

  • --output with any value other than json exits 1. listen --output is unchanged.
  • connection update fails when --source-id or --destination-id differs from the stored value, and connection upsert fails when the destination differs. The API never changes an existing connection's source or destination.
  • If you put --rule-filter-* before --rule-transform-* and relied on the transform running first, reorder the flags.

The release notes list every change, including fixes to source auth flags on several source types.

npm install -g hookdeck-cli@latest
# or
brew upgrade hookdeck