Update Ticket
Updates a ticket's status, priority, assignment and category.
Endpoint
PUT /api/ticketAuthentication
Requires API token authentication
Requires the Scale plan or above (see API)
Subject to rate limiting
Request Body
ticketId
string
Yes
The unique identifier of the ticket
status
string
No
New ticket status
priority
number
No
New priority level
categoryId
string
No
ID of the category to assign
assignedTo
string
No
ID of the agent to assign
Valid Values
status:"Open","Resolved","Pending","Waiting"priority:1,2,3categoryId: Must be a valid category ID from GET /categoriesassignedTo: Theidof an agent from GET /agents. Omit to leave assignment unchanged, ornullto make the ticket unassigned
Note:
assignedTotakes an agent ID (obtained from GET /agents), not an email address. This allows agents who signed up with a wallet — and therefore have no email — to be assigned tickets. Passing an email (or any value that is not a valid agent ID) returns a validation error.
Response
Success (200 OK)
Error Responses
Ticket not found (400)
Invalid category (400)
Invalid status/priority (400)
Assignee not found (400)
Unauthorized (401)
Returned when the API key is missing or invalid.
Plan too low (403)
Server error (500)
Behavior
Each change (status, priority, category, assignment) creates an audit log message
Changes only apply when new values differ from existing values
Categories must be active and associated with the client
assignedTois resolved to an agent in your organization. An ID that does not belong to your organization is rejected withAssignee not foundAssigning a ticket that the AI is actively handling ends AI handling (the ticket is handed off to the agent)
Example (cURL)
Last updated
Was this helpful?