Team questions
List team questions
Questions agents left for the team through the ask_team tool, newest first. Filter by status=open to build the queue of what waits for an answer. Sensitive values are covered in the question and the context. Read only and safe to repeat. To let an agent ask, grant it the ask_team tool: PUT /v2/agents/{id}/tools/ask_team.
Required scope: team-questions:read.
query Parameters
limitcursorThe nextCursor of the previous page, with the same filters.
statuscaseIdHeaders
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
List team questions › Responses
objecthasMorenextCursorRetrieve a team question
The question, what the agent was trying to do, and the answer once there is one. Sensitive values are covered. Read only and safe to repeat.
Required scope: team-questions:read.
path Parameters
id^tqn_[0-9A-Za-z]{22}… · requiredThe id of the team question (tqn_…).
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Retrieve a team question › Responses
objectidstatusopen waits for an answer. answered has the answer and the agent has not told the person yet. delivered: the agent told the person. discarded: it was closed without telling the person, for example because a human took the case.
caseIdquestionWhat the agent needs to know, written for a person who did not see the conversation.
contextWhat the agent is trying to do and why it asks.
answeranswerTitleansweredByWho answered: a member (mbr_ is not exposed here) or an API key (key_).
answeredAtdeliveredAtcreatedAtupdatedAtRead a team question with its context
Everything a person needs to answer: the question, what the agent was trying to do, the last lines of the conversation with the customer and the data of the case. Every sensitive value is covered, in the text and in the data: only the name of the field shows. Needs the scopes team-questions:read, conversations:read and cases:read. Read only and safe to repeat.
Required scopes: team-questions:read, conversations:read, cases:read.
path Parameters
id^tqn_[0-9A-Za-z]{22}… · requiredThe id of the team question (tqn_…).
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Read a team question with its context › Responses
objectidstatuscaseIdcontactNamepipelineNamequestionThe question, with every sensitive value covered.
contextanswercreatedAtThe last lines of the conversation with the customer, oldest first. Internal notes are left out.
The data of the case that is not sensitive, with the name of each field.
hiddenFieldsNames of the fields that hold sensitive values. Their values never appear here.
Answer a team question
Gives the agent the answer. The agent resumes the conversation and tells the person with its own words, through the channel of the case; nothing is forwarded raw. Use it from the tool where your team works, for example Jira. Not idempotent: a question is answered once and a second answer is 409 team_question_not_open. It does not create a knowledge document.
Required scope: team-questions:write.
path Parameters
id^tqn_[0-9A-Za-z]{22}… · requiredThe id of the team question (tqn_…).
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Idempotency-KeyMakes the request safe to retry. Once it starts running, its final response (2xx, 4xx or 5xx) is kept for 24 hours and the same key gets it back, without repeating the effect. A request rejected before it runs leaves the key free. A replayed create omits the secret. The same key with a different request is rejected with 409 idempotency_key_reused.
Answer a team question › Request Body
answerThe answer, written as a colleague would say it. The agent does not forward it: it tells the person in its own words, in the context of the conversation.
titleA title for the answer. Optional. Saving the answer as knowledge is a separate step: this does not create a knowledge document.
Answer a team question › Responses
objectidstatusopen waits for an answer. answered has the answer and the agent has not told the person yet. delivered: the agent told the person. discarded: it was closed without telling the person, for example because a human took the case.
caseIdquestionWhat the agent needs to know, written for a person who did not see the conversation.
contextWhat the agent is trying to do and why it asks.
answeranswerTitleansweredByWho answered: a member (mbr_ is not exposed here) or an API key (key_).
answeredAtdeliveredAtcreatedAtupdatedAt