# Call follow-up

> ⚠️ **The methods ship in the `call 26.600.0` update and are not yet available on all Bitrix24 accounts.** If the update has not reached your Bitrix24 account, the API returns `422 METHOD_NOT_YET_AVAILABLE` — this means the method has not been released on the account yet, not an integration error.

Read the AI Follow-up of completed calls: transcription, meeting overview, summary, insights, and efficiency evaluation. The methods only read data and change nothing.

**Scope:** `call` | **Base URL:** `https://vibecode.bitrix24.com/v1` | **Authorization:** `X-Api-Key`

## Operations

- [Follow-up list](./followup/list.md) — `POST /v1/calls/followups/list`
- [Follow-up for a single call](./followup/get.md) — `GET /v1/calls/followups/:callId`

## Access

The `call` scope is required. It does not extend data visibility: the method still checks permissions for each specific call. A user sees the Follow-ups of the calls they took part in, or of the calls whose linked chat they are a member of — including when they were added to the chat after the conversation. A Bitrix24 account administrator sees all Follow-ups of the account.

## Insights

Participant analysis — `insights.speakerAnalysis`, meeting strengths and weaknesses, recommendations — is not available on every Bitrix24 account. When it is unavailable, `insights.speakerEvaluationAvailable` is returned as `false`, and the response structure does not change.

## Typical scenario

1. Get the list for a period: [`POST /v1/calls/followups/list`](./followup/list.md) with a filter on the start date. Take the `callId` of the call you need from the response.
2. Request the full data: [`GET /v1/calls/followups/:callId`](./followup/get.md). If you do not need all blocks, limit the output with the `select` parameter.

## See also

- [Calls](/docs/calls)
- [Call transcript for a client](/docs/entities/activities/transcript)
- [Errors](/docs/errors)