---
title: "Retrieve a call status"
method: GET
path: "/calls/{call_control_id}"
tags: ["Call Information"]
---

# Retrieve a call status

`GET /calls/{call_control_id}`

Returns the status of a call (data is available 10 minutes after call ended).

## Path parameters

- `call_control_id` string, required

## Response `200`

Successful response with details about a call status.

- object
  - `data` Call
    - `call_control_id` string, required — Unique identifier and token for controlling the call.
    - `call_duration` integer — Indicates the duration of the call in seconds
    - `call_leg_id` string, required — ID that is unique to the call and can be used to correlate webhook events
    - `call_session_id` string, required — ID that is unique to the call session and can be used to correlate webhook events. Call session is a group of related call legs that logically belong to the same phone call, e.g. an inbound and outbound leg of a transferred call
    - `client_state` string — State received from a command.
    - `end_time` string — ISO 8601 formatted date indicating when the call ended. Only present when the call is not alive
    - `is_alive` boolean, required — Indicates whether the call is alive or not. For Dial command it will always be `false` (dialing is asynchronous).
    - `record_type` 'call', required
    - `start_time` string — ISO 8601 formatted date indicating when the call started

## Other responses

- `422` — Unprocessable entity. The request was well-formed but could not be processed due to semantic errors. This includes validation errors, invalid parameter values, call state errors, conference errors, queue errors, recording/transcription errors, and business logic violations.
- `default` — Unexpected error

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/1571b0380bd7/schema)