Skip to main content
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

Authorization
string
header
required

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

Path Parameters

ticket_id
string
required

Existing ticket to process. Must be open and unarchived. The current assignee is preserved.

Body

application/json
instructions
string | null

Optional instructions, up to 20000 bytes. Omit to review the ticket and take the next appropriate step.

idempotencyKey
string

Required retry key (1-200 bytes), unique per ticket and caller. Reuse with identical instructions to retry safely.

Response

200 - application/json

Success

data
data · object