---
updatedAt: 2025-07-15T16:13:40.000Z
agentTools:
  projectIndex: https://developers.kaleyra.io/llms.txt
---

# Call Log Pull API

GET Method

> 📘 Note:
>
> This feature is currently not available for users registered in the North America (NA) region.

Kaleyra.io lets you access the call log of your Kaleyra account via the UI (Channel>Voice>Logs screen). Logs screen displays information like the type of call, from and to numbers, call start time, bridge number, call status, duration of the call, and the credits utilized for the call.

The same can be achieved using the Call Log Pull API. Kaleyra.io offers the Call Log Pull API to access the call log details of your Kaleyra account for a period of 7 days using parameters like start time, end time, status, and so on.

## Base URL

**`<https://api.kaleyra.io/v1/><SID>`**

1. Signup or Login to Kaleyra.io and create your API key

***

Refer to the [Create an API Key](https://developers.kaleyra.io/docs/generating-an-api-key) page for steps to create your API key. To view the API Key and the SID, see [View API Key and SID](https://developers.kaleyra.io/docs/view-api-key-and-sid).

> 📘 Note:
>
> After you sign up, your account will be on the trial version. You must [complete the KYC](https://developers.kaleyra.io/docs/document-submission-and-approval) to access all the features in Kaleyra.io.After you sign up, your account will be on the trial version. You must complete the KYC to access all the features in Kaleyra.io.

2. API request to  access the call log details

***

## Request Format

To get the call log, use the following **voice/call-logs** endpoint.

```curl
curl -X GET '<URL>/v1/<SID>/voice/call-logs' \
-H 'Content-Type: <CONTENT_TYPE>' \
-H "api-key: <API_KEY>" \
-H 'limit: <LIMIT>' \
-d 'status=<STATUS>' \
-d 'call_id=<CALL_ID>' \
-d 'start_time=<START_TIME>' \
-d 'end_time=<END_TIME>' \
-d 'page=<PAGE>' \
-d 'offset=<OFFSET>' \
-d 'bridge=<BRIDGE>'
```

Provide the details listed in the Parameters and Variable section.

## Parameters and Data Types

Following is the list of parameters and data types supported:

<Table align={["left","left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Parameter
      </th>

      <th>
        Data Type
      </th>

      <th>
        Description
      </th>

      <th>
        Example
      </th>

      <th>
        Mandatory?
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `SID`
      </td>

      <td>
        String
      </td>

      <td>
        Account SID (Security Identifier). Generated by Kaleyra.io while creating an API key.
      </td>

      <td>
        HXEPXXXXXX1US
      </td>

      <td>
        True
      </td>
    </tr>

    <tr>
      <td>
        `CONTENT_TYPE`
      </td>

      <td>
        String
      </td>

      <td>
        Indicates the format of the content the API will be processing.
      </td>

      <td>
        application/x-www-form-urlencoded
      </td>

      <td>
        True
      </td>
    </tr>

    <tr>
      <td>
        `API_KEY`
      </td>

      <td>
        Alphanumeric
      </td>

      <td>
        API key generated from Kaleyra.io account
      </td>

      <td>
        Axxxxxxxxxxxxxxxxxxxxxxxxxxxx3
      </td>

      <td>
        True
      </td>
    </tr>

    <tr>
      <td>
        `LIMIT`
      </td>

      <td>
        Integer
      </td>

      <td>
        Limit of records to be listed/fetched for each API call, default is 25.
      </td>

      <td>
        25
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `STATUS`
      </td>

      <td>
        String
      </td>

      <td>
        Status of the call. In the case of multiple call statuses, ensure they are comma-separated.
      </td>

      <td>
        ANSWER\
        or\
        NOANSWER
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `CALL_ID`
      </td>

      <td>
        String
      </td>

      <td>
        Valid call ID. In case of multiple call IDs, ensure they are comma-separated.
      </td>

      <td>
        75xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-x
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `START_TIME`
      </td>

      <td>
        Date and Time
      </td>

      <td>
        Start time for the call log.  

        Note that you can pull logs for up to seven days including the current day.  

        The format is [2013-03-15T00:00:00+00:00 (Format: Y-m-d\TH:i:sP)]  

        Default is current time in 24 hr format.
      </td>

      <td>
        2020-07-28T10:16:25Z,2020-08-12T15:16:25Z
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `END_TIME`
      </td>

      <td>
        Date and Time
      </td>

      <td>
        End time for the call log.  

        Note that you can pull logs for up to seven days including the current day.  

        The format is [2013-03-15T00:00:00+00:00 (Format: Y-m-d\TH:i:sP)]  

        Default is current time in 24 hr format.
      </td>

      <td>
        2020-07-29T10:16:25Z,2020-08-12T15:16:25Z
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `PAGE`
      </td>

      <td>
        Integer
      </td>

      <td>
        Total number of pages that you want to access.
      </td>

      <td>
        4
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `OFFSET`
      </td>

      <td>
        Integer
      </td>

      <td>
        Number of records that should be skipped while displaying data on the second page onwards.
      </td>

      <td>
        20
      </td>

      <td>
        False
      </td>
    </tr>

    <tr>
      <td>
        `BRIDGE`
      </td>

      <td>
        Integer
      </td>

      <td>
        The DID number to be used for originating the call, should be an Active subscribed number.\
        The number must contain the format as Country Code followed by Mobile Number.
      </td>

      <td>
        13236xxxxx7
      </td>

      <td>
        False
      </td>
    </tr>
  </tbody>
</Table>

## Sample Success Response

**Call Log Pull success response**

```json
{
    "status": 200,
    "code": "RBC103",
    "message": "Request successfully executed!",
    "data": [],
    "error": {},
    "total": 0,
    "offset": 0,
    "limit": 25,
    "page": 1
}
```

## Sample Failure Response

**Call Log Pull failure response with an invalid SID or API key**\
If your response fails due to the invalid SID or API key, re-execute the command with a valid SID or API key.

```json
{
    "code": "RBC001",
    "message": "Incorrect SID or API key.",
    "data": [],
    "error": {
        "error": "Incorrect SID or API key."
    }
}
```

**Call Log Pull failure response when incorrect start time is provided**\
If your response fails due to the invalid values, re-execute the command with valid values.

```json
{
    "code": "RBC3004",
    "message": "Incorrect start time.",
    "data": [],
    "error": {
        "error": "Incorrect start time."
    }
}
```

## HTTP Status Code and Response Code

For more information regarding the HTTP Status Codes and Response Codes, refer to [Voice Error Codes](https://developers.kaleyra.io/docs/voice-error-codes).