Skip to main content
GET
/
api
/
v1
/
calls
/
sid
/
{call_sid}
Get Call By Sid
curl --request GET \
  --url https://api.example.com/api/v1/calls/sid/{call_sid} \
  --header 'Authorization: Bearer <token>'
{
  "call_sid": "<string>",
  "to_phone_number": "<string>",
  "customer_phone_number": "<string>",
  "id": 123,
  "assistant_id": 123,
  "status": "<string>",
  "call_meta": {},
  "duration": 123,
  "started_at": "2023-11-07T05:31:56Z",
  "ended_at": "2023-11-07T05:31:56Z"
}
This endpoint retrieves a single call record by its unique Twilio Call SID. This is useful when you have the SID from Twilio’s webhooks or logs and need to look up the corresponding call in your system.

​
Path Parameters

  • call_sid (string, required): The unique Call SID from Twilio.

​
Response

The response is a JSON object containing the full details of the specified call. The structure is the same as the objects returned by the List Calls endpoint.
Response
{
  "id": 101,
  "call_sid": "CAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "assistant_id": 123,
  "to_phone_number": "+15551234567",
  "customer_phone_number": "+15559876543",
  "status": "completed",
  "started_at": "2023-10-30T10:00:00Z",
  "ended_at": "2023-10-30T10:05:00Z",
  "duration": 300,
  "cost": 0.05,
  "metadata": {
    "customer_id": "cust_abc123"
  },
  "created_at": "2023-10-30T10:00:00Z",
  "updated_at": "2023-10-30T10:05:00Z"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
call_sid
string
required

Response

Successful Response

Schema for call response.

​
call_sid
string
required
​
to_phone_number
string
required
​
customer_phone_number
string
required
​
id
integer
required
​
assistant_id
integer
required
​
status
string
required
​
call_meta
Call Meta · object
​
duration
integer | null
​
started_at
string<date-time> | null
​
ended_at
string<date-time> | null