Get conversation status counts
GET /api/workspaces/{workspaceId}/conversations/status-counts
Get aggregate conversation counts by status for a workspace. Useful for building dashboards.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace to get status counts for.
Responses
Section titled “ Responses ”Aggregate conversation counts by status.
Aggregate conversation counts by status for a workspace.
object
Number of conversations in open status.
Example
12Number of conversations currently in progress.
Example
8Number of conversations awaiting a response from the contact.
Example
23Number of resolved conversations.
Example
156Number of closed conversations.
Example
4Number of abandoned conversations.
Example
2An API key restricted to a brand or workspace named a workspace outside its restriction, or one that is not a workspace of your account (Workspace not found).
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"]