Ticket API
Trigger Ticket Agent
Ask Serval to process an existing open ticket, including human-assigned tickets. The current assignee is preserved and paused AI resumes. The trigger and optional instructions create no ticket message or notification. Serval may reply and take its normal actions. Returns when accepted; processing is asynchronous and remains subject to normal agent policies. Retry with the same idempotencyKey and instructions.
POST
Trigger Ticket Agent
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
Requires visibility into the ticket and permission to trigger the agent on its team. The ticket must be open and unarchived; its current assignee is preserved.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Existing ticket to process. Must be open and unarchived. The current assignee is preserved.
Body
application/json
Response
200 - application/json
Success

