Skip to main content
GET
Get Conversation Statistics
What it does: Returns everything about one call — whether the phone connected, the business outcome code, and the full transcript. You need: A conversationId from Get Conversation Logs or a post-call webhook (conversation_id). After Trigger Call, poll Logs with your clientReferenceId to find the conversationId.

Required Permission

conversations

Path Parameters

Minimum working example

The three fields developers ask about

Calls produce three different kinds of outcome data. They answer different questions:

overallCallDisposition — what is it?

A short outcome code assigned after the call, based on your agent’s disposition configuration. It is not a sentence — it is a token you map in your CRM and reporting pipeline.

Disposition codes

Standard overallCallDisposition values:
Your agent’s disposition prompt may produce additional codes beyond this list. Treat unknown values as opaque strings and log them for mapping. The same code appears as STAGE_CODE and inside disposition_result in post-call webhooks (snake_case) — see Update Agent — Post-call webhook.

callSummary — what is it?

An optional LLM-generated wrapper. When present, callSummary.disposition gives a human-readable label (e.g. "resolved"). When analytics have not finished processing, callSummary is null — this is normal on recent calls. Use overallCallDisposition for programmatic logic. Use callSummary.disposition only when you need a readable label and the object is present.

utteranceAnalytics — what is it?

The full conversation transcript as an array of turns. Each entry has: Same shape as transcript in Logs, but Stats always returns the complete record.
Post-call webhooks deliver the same data in snake_case (conversation_id, detected_language, STAGE_CODE). See Update Agent — Post-call webhook for the webhook payload and field mapping.

Response

Success (200)

Verified example:
callSummary, averageAgentLatency, callProcessed, and lastProcessedOn are not shown above because they are populated asynchronously and may be absent on recent calls. When present:

All response fields

Edge cases

Errors

403 Forbidden
404 Not Found
Save the requestId from every response. You will need it if you contact Gnani support to trace a specific request.

Authorizations

x-api-key
string
header
required

API key with 'conversations' permission

Path Parameters

conversationId
string
required

Unique identifier of the conversation.

Response

Conversation statistics retrieved successfully

status
string
Example:

"success"

requestId
string
message
string
Example:

"Conversation details fetched successfully"

response
object[]