Decide a webchat conversation’s pending proposal
Approves or denies one proposal waiting in a webchat conversation, exactly as Activity would: approve starts it as a task of that conversation and answers executing (a proposal with followUp takes that follow-up, with the caller as the one it follows up for, and answers succeeded with it), deny drops it and runs nothing. While the agent already runs as many tasks as it may, approval is refused with 409 SUBSESSION_LIMIT and the proposal keeps waiting. Whichever surface answers first decides it: one that expired or was already decided is refused with 409 and runs nothing, and a proposal of another conversation answers 404. Only callers who may continue that conversation, or who can edit the agent, may decide, and they are recorded as the decider. Answers 409 DAEMON_FEATURE_MISSING when the agent’s daemon cannot bind a decision to one conversation.
授权
bearerAuth 位置: header
路径参数
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuid1 <= length <= 5121 <= length <= 512请求主体
application/json
TypeScript 定义
在 TypeScript 中使用 request body 类型。
响应主体
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/orgs/string/agents/497f6eca-6276-4993-bfeb-53cbbbba6f08/assistant/conversations/string/proposals/string/decision" \ -H "Content-Type: application/json" \ -d '{ "decision": "approve" }'{ "status": "awaiting_review", "failure": "string", "followUp": { "id": "string", "conversation": { "sessionId": "string", "title": "string", "platform": "string", "channelName": "string" } }}