Skip to content
2 minute readNewAgent-ready

Webhooks for approvals, disputes and price proposals

Three new webhook events tell your own tools when a person has something to act on: an agent call waiting for approval, a dispute opened, and a price change proposed. Route them to a chat channel, a pager or a ticket queue.

The webhook event list with approval requested, dispute opened and price proposal created at the top

Until now an agent call held for approval waited for someone to open the dashboard. Subscribe a webhook endpoint to these events and your own tools hear about it the moment it happens.

  • `approval.requested`: an agent or API key call is held until a person approves it. The event carries the action, the request method and path, when it expires, and a link to approve or reject it. The request body is not included; read it from the approval.
  • `dispute.opened`: a dispute was opened against a payment, with its amount, currency, status and reason.
  • `price_proposal.created`: the commerce control plane proposed a price change, with the current and proposed price. One event per proposal.

Each event is signed like every other webhook and has an id derived from the record it is about, so if one ever arrives twice you can drop the repeat by its id. Endpoints that subscribe to every event receive them automatically; others can add them in Webhooks.

The webhooks feature page now lists only events that are actually sent.