ticket_status_changed

Sent when the status of a ticket changes. The change can happen while the ticket is edited and saved, or while it is dragged to another column on the board (kanban). No event is sent if the status stays the same.

Use it for resolution time measurement and status based automations.

Sample body

scenario: ticket_status_changed

{
  "ticket_id": 1542,
  "old_status_id": 4,
  "new_status_id": 5,
  "actor_type": "user",
  "actor_id": 27
}

Send this body to your own address

The sample body above is sent to the address below as a POST request. The request goes from your browser, so the response cannot be read if the receiving endpoint sends no CORS header; the request itself still arrives. Use the cURL equivalent to try it from the server side.

cURL equivalent:

curl -X POST 'https://your-address.example/webhook' \
  -H 'Content-Type: application/json' \
  -d '{"ticket_id":1542,"old_status_id":4,"new_status_id":5,"actor_type":"user","actor_id":27}'

Fields

Field	Type	Description
ticket_id	number	Unique identifier of the ticket.
old_status_id	number	Identifier of the status before the change.
new_status_id	number	Identifier of the new status.
actor_type	string	Type of whoever made the change: user, account or system_user. null when unknown.
actor_id	number	Identifier of whoever made the change. null when unknown.

Mapping status names

The body carries the identifiers of the statuses, not their names. To turn the identifiers into names, fetch the ticket statuses of the project once and keep them.