Skip to main content
POST
Attach a workspace to an AI ticket

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

authorization
string | null
x-ankra-organisation-id
string | null

Path Parameters

ticket_id
string<uuid>
required

Body

application/json
workspace_id
string<uuid>
required

Response

Successful Response

id
string<uuid>
required
ticket_number
integer
required
title
string
required
body
string
required
kind
string
required
status
string
required
priority
string
required
assignee_agent_task_id
string<uuid> | null
required
assignee_agent_name
string | null
required
assignee_user_id
string | null
required
assignee_user_email
string | null
required
assignee_user_name
string | null
required
parent_ticket_id
string<uuid> | null
required
parent_ticket_number
integer | null
required
sub_ticket_count
integer
required
open_sub_ticket_count
integer
required
cluster_id
string<uuid> | null
required
cluster_name
string | null
required
cluster_archived
boolean
required
alert_id
string<uuid> | null
required
source_kind
string | null
required
source_id
string | null
required
plan_document
string | null
required
plan_status
string
required
workspace_id
string<uuid> | null
required
slack_channel_id
string | null
required
slack_thread_ts
string | null
required
teams_conversation_id
string | null
required
labels
string[]
required
staffing
enum<string>
required

Who works this ticket: 'auto' (the AI team may staff it, mirror it into the organisation's bound Slack/Teams thread, and escalate it when stale) or 'manual' (a human owns it; all three automatic lanes skip it).

Available options:
auto,
manual
due_at
string<date-time> | null
required

Advisory due date. No loop reads it; it is metadata for the humans on the board.

created_by_kind
string
required
created_by
string
required
resolution
string | null
required
recurrence_count
integer
required
last_event_sequence
integer
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
closed_at
string<date-time> | null
required
status_changed_at
string<date-time>
required
decision_request
AiTicketDecisionRequest · object | null
required

Set while the ticket is blocked on a choice the agent offered; null otherwise. Answer it with POST /ai-tickets/{ticket_id}/decision.

condition_check
AiTicketConditionCheck · object
required

Whether what the ticket is about still holds, derived when the ticket is read from the bound cluster, the linked alert and the newest observation of its condition. Never null.