API reference / Support Agent
Make a bug ticket of a chat
Makes an engineering ticket, kind bug and label support, of a problem that a visitor reports in the chat. The Engineer analyzes and plans it, and reads the report and the chat on its card. A person always approves its plan, and Troopy never releases it by itself, because the words of a visitor steer it. A chat has one open ticket: while it is open, a new report goes on it (added: true). The Support agent makes 5 tickets a day in a workspace. People make more. brief: what the visitor saw, where, and what they tried. Mark each detail that is not known as not known.
/api/v1/support-conversations/{id}/ticketOther ways to call it
troopy support tickettroopy_file_support_ticketIdempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.Path parameters
id*stringA 24-character id
Body
application/jsonbrief*stringWhat the visitor saw, where, and what they tried, 2,000 characters at most
At least 10 characters · At most 2000 characters
wherestringThe page or the part of the product, such as /checkout
At most 80 characters
Response
201 · application/jsondata*object2 properties
ticket*object7 properties
key*stringtitle*stringstatus*enum<string>backlogtodoin_progressneeds_youin_reviewdonecanceled
stage*enum<string> | nullThe step of the engineering flow. Null: the ticket is not in the flow
analyzeplanbuildtestrelease
reports*integerThe reports of the visitor's problem that the ticket holds
liveAt*string | nullWhen the ticket went live. The team then tells the visitor that the problem is fixed
told*booleanA person of the team replied to the visitor after the ticket went live
added*booleantrue: the report went on the open ticket of the chat