---
title: "Export call records"
method: GET
path: "/v1/projects/{projectId}/calls/export"
tags: ["Calls"]
---

# Export call records

`GET /v1/projects/{projectId}/calls/export`

## Request

- Base URL: `https://elastic-trunking.api.sinch.com`
- URL: `https://elastic-trunking.api.sinch.com/v1/projects/{projectId}/calls/export`
- Auth: one of:
  - HTTP basic
  - OAuth 2
    - Client credentials
    - Token URL: `https://auth.sinch.com/oauth2/token`

Export call records for a project. This returns a comma separate value (CSV) response. You can specify which records to export using the query parameters.

## Path parameters

- `projectId` string, required

## Query parameters

- `from` string, phonenumber
- `to` string, phonenumber
- `trunkId` string
- `createTime` string
- `callResult` 'COMPLETED' | 'NO_ANSWER' | 'CANCEL' | 'BUSY' | 'FAILED': The result of the call.
- `direction` 'INBOUND' | 'OUTBOUND': Filter results based on the call direction. Describes whether the call was `INBOUND` *to* your Sinch number or was `OUTBOUND` and made *from* your Sinch number. An `INBOUND` call can also come from a SIP infrastructure or an application built using the Sinch SDK. An `OUTBOUND` call can be placed to a SIP infrastructure or an application built using the Sinch SDK.
- `page` integer
- `size` integer
- `fromCountryCode` string
- `toCountryCode` string
- `emergencyOnly` 'true' | 'false'
- `region` string
- `projectIds` string
- `fileName` string
- `groupId` string
- `parentId` string
- `relationshipType` string
- `hasChildren` 'true' | 'false'

## Response `200`

OK

## Changes

- **2026-10-01** `108d6bcb3948`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/sinch/apis/elastic-sip-trunk-api/changes/v1/projects/:projectId/calls/export/get.md)

---

[API](https://skmtc.dev/sinch/apis/elastic-sip-trunk-api.md) - [All operations](https://skmtc.dev/sinch/apis/elastic-sip-trunk-api/llms.txt) - [OpenAPI document](https://skmtc.dev/sinch/apis/elastic-sip-trunk-api/revisions/8f15a650c7cd?raw)