Update a ticket

status takes the state you want; an illegal move for the state it is in answers 409 rather than silently doing nothing. Fields are applied in a fixed order with status last, so assigning and solving in one call fires the solve with the assignee already set.

Path parameters

Request body

Response 200

Errors

• 400 — Invalid body, or nothing to update
• 401 — Missing or invalid API key
• 404 — Not found
• 409 — That move is not legal from the ticket’s current state
• 429 — Rate limit exceeded

Every error shares one envelope.

Example

curl -X PATCH \
  https://www.hey.support/api/v1/tickets/<id> \
  -H 'Authorization: Bearer hs_live_…' \
  -H 'Content-Type: application/json' \
  -d '{"status":"open","priority":"low"}'