List Autopilot Runs
GET/api/support/agent/tickets/:ticket/ai/runs
Lists the AI agent's autopilot sessions on a ticket, newest first (at most 50). The AI agent reads this after a cold start to pick up its run count and the last run's outcome; the console shows it as the run history. Triage and draft suggestions are not included.
support:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Path parameters
ticket(integer) — the ticket id.
No query parameters, no pagination.
Each run has id, kind (always autopilot), status (pending while the session runs; done, failed or skipped once finished), model, output (the result summary object, or null), run_number (the per-ticket run count), started_at, finished_at, cost_usd (number, or null), outcome (the runner's short code for how the session ended, e.g. awaiting_reply_approval, session_error) and created_at. accepted and decisions are always null on autopilot runs.
Authentication: Bearer token with the support:read scope belonging to any support agent (viewers included); a non-agent gets a 403. No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.