Get conversation quality
GET /api/conversations/{conversationId}/quality
Retrieve the CSAT score for a single conversation. Scores are computed after the conversation is resolved.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the conversation.
Responses
Section titled “ Responses ”The conversation quality score.
CSAT score for a single conversation, computed after resolution.
object
The conversation this score belongs to.
Example
c9f8e7d6-b5a4-3210-fedc-ba9876543210How well the customer’s problem was resolved (1.0 to 5.0).
Example
4.5How smooth and efficient the interaction was (1.0 to 5.0).
Example
4.2How well the tone, language, and presentation met expectations (1.0 to 5.0).
Example
4Weighted average of the three dimension scores.
Example
4.23Gap between expected and perceived service level (0.0 to 1.0, lower is better).
Example
0.08How confident the model is in the computed scores (0.0 to 1.0).
Example
0.87Number of conversation signals used to derive the scores.
Example
6Timestamp when the score was computed.
Example
2026-03-15T14:35:00.000ZNo quality score exists for this conversation.
Standard error response returned by all endpoints on failure.
object
A human-readable error message describing what went wrong.
Example
Conversation not foundA machine-readable reason on some refusals, for example ‘key_lock’ when an API key’s brand or workspace restriction does not cover the action.
Example
key_lockOn a 403 for an API key without a scope the endpoint requires: the scopes the key lacks.
Example
[ "mcp:write"]On a 409 with code duplicate_question or duplicate_rule_text: the knowledge base entry or policy that already holds the question or rule text.
Example
11223344-5566-4788-99aa-bbccddeeff00On a 422 about one MCP connection a request names, from an assignment or an agent create or update (a connection that does not exist, one listed twice, or one that does not declare a tool named): the connection, as the request named it.
On the same 422: the tool names the connection does not declare.
Example
[ "get_orders"]On the same 422: the tools the connection declares.
Example
[ "get_order", "search_orders"]