Merge Agent Conversation Tickets

Changed on

Merge other open issues of the same agent into this pending, in-progress, or resolved one. Their conversations move onto this issue, its priority is raised to the highest among them, and they are kept with status 'merged'. Requires viewer access to the issue's agent.

post/v1/convai/triage-tickets/{agentqa_ticket_id}/merge

Request

  • Base URL
    https://api.elevenlabs.io (the document declares no server; this is the origin it was published from)
  • Auth
    none declared

Path parameters

agentqa_ticket_idstring required

Headers

xi-api-keystring nullable

Your API key. This is required by most endpoints to access our API programmatically. You can view your xi-api-key using the 'Profile' tab on the website.

Request body

source_ticket_idsstring[] required

Open issues of the same agent to fold into this one. They are kept with status 'merged', pointing at this issue.

Response

Successful Response

agentqa_ticket_idstring required
workspace_idstring required
owner_user_idstring required
agent_idstring required
needs_clusteringboolean required
titlestring nullable required

One-line headline for the agent issue. None only on issues created before titles existed.

issue_typeunknown
labelsstring[] required
conversation_idsstring[] required
first_seen_unix_secsinteger nullable required
last_seen_unix_secsinteger nullable required
qa_commentstring nullable required
status'open' | 'in_progress' | 'resolved' | 'cancelled' | 'merged' required
priority'low' | 'medium' | 'high' | 'urgent' nullable required
merged_into_ticket_idstring nullable

The agent issue this one was merged into, set while its status is 'merged'.

source'qa' | 'agent' | 'manual' required
assignee_user_idstring nullable required
created_at_unix_secsinteger required
updated_at_unix_secsinteger required

Changes

    • breaking

      the response property issue_type became nullable for the status

    • breaking

      the response property issue_type became optional for the status

    • info

      removed subschema #2 from the issue_type response property anyOf list for the response status

    1 more change in this revision