> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transcript Analysis

## URL

The API follows REST conventions. Perform an HTTPS GET to the URL in order to retrieve Transcript Analysis. Currently, the transcript summary will be returned if it is available. The following response formats are supported, where CUID-33 is the call record id.

<table><thead><tr><th>Format</th><th>Description and URL</th></tr></thead><tbody><tr><td>json (default)</td><td>Returns a JSON object of the transcript analysis. `https://mynetwork.invoca.net/call/transcript_analysis/CUID-33`</td></tr></tbody></table>

## Authentication

The API uses OAuth to validate access. The OAuth Token can be passed in two ways. The first way is to pass the OAuth Token in the header of the request. The second is to pass the OAuth Token like any other query parameter. Please note that the OAuth Token is a required parameter. OAuth Tokens may be generated from the Manage API Credentials page.

## Response

> [accordion] Get a transcript analysis (transcript summary available)
>
> #### Examples
>
> Get transcript analysis for the given call record `CUID-33` and a summary is available
>
> Endpoint:
>
> `https://mynetwork.invoca.net/call/transcript_analysis/CUID-33`
>
> Format: application/json
>
> Response Code: 200
>
> Response Body:
>
> ```json theme={null}
> {
>    "call_record_id": "CUID-33",
>    "transcript_summary": "The customer was looking to purchase a new vehicle."
> }
> ```

> [accordion] Get a transcript analysis (no transcript summary available)
>
> #### Examples
>
> Get transcript analysis for the given call record `CUID-33` and no summary is available
>
> Endpoint:
>
> `https://mynetwork.invoca.net/call/transcript_analysis/CUID-33`
>
> Format: application/json
>
> Response Code: 200
>
> Response Body:
>
> ```json theme={null}
> {
>    "call_record_id": "CUID-33"
> }
> ```

Endpoint:

`https://mynetwork.invoca.net/call/transcript_analysis/<call_record_id>`


## Related topics

- [Transcript Analysis (v2)](https://docs.invoca.com/developers/2026-02-01/api_documentation/call_api/transcript_analysis_v2_api.md)
- [Summarize](https://docs.invoca.com/invoca-design-system/ai-experience/actions/summarize.md)
- [Call API](https://docs.invoca.com/developers/2026-02-01/api_documentation/call_api/index.md)
- [Creating AI Signals in Signal AI Studio](https://docs.invoca.com/s/article/creating-ai-signals-signal-ai-studio.md)
- [Verification](https://docs.invoca.com/invoca-design-system/ai-experience/governors/verification.md)