List support tickets for the organization
Authorization
bearerAuth tickets:readOrg-scoped API key generated in Settings → API Keys (al_live_ prefix). Shared with the MCP server — the same key authenticates both surfaces. A key carries a set of least-privilege scopes; each operation lists the scope it requires. A key missing a required scope gets 403 with a WWW-Authenticate: Bearer error="insufficient_scope" header. Scope catalogue: see the x-api-scopes object and /.well-known/oauth-protected-resource.
In: header
Scope: tickets:read
Query Parameters
Value in
- "open"
- "in_progress"
- "resolved"
- "closed"
- "duplicate"
Value in
- "critical"
- "high"
- "medium"
- "low"
Value in
- "bug"
- "feature_request"
- "documentation"
- "how_to"
- "general_question"
Max results per page
1 <= value <= 2010Opaque value from a previous response's next_cursor. Omit for the first page.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/agent/tickets"{ "tickets": [ { "id": 0, "content": "string", "category": "string", "priority": "string", "status": "string", "ai_summary": "string", "created_at": "string" } ], "next_cursor": "string"}{ "error": { "message": "string", "code": "rate_limited" }}{ "error": { "message": "string", "code": "rate_limited" }}{ "error": { "message": "string", "code": "rate_limited" }}Get the organization's most recently generated FAQ digest
Previous Page
Open a new support ticket on behalf of a user
Runs through the same AI triage/answer pipeline as every other channel (Discord, Slack, email) — the ticket may get auto-answered if confidence is high, otherwise it queues for human review.