Skip to main content
GET
Export all data about a contact
Returns the personal data we hold about one contact as a single JSON document. Use it to answer a data subject access request: the person asked what you know about them, and this is the machine-readable answer. A few kinds of record are deliberately left out, such as deleted records and internal archives; see What is not in the export. The API key needs both read:contacts and read:conversations: the export hands over every conversation’s transcripts, recordings and analyses, which the conversation routes keep behind read:conversations. The same export is available in the app: open the contact and choose Export data.

What the export contains

Each conversation carries its call attempts, and each call attempt its transcript and a recordingUrl. The conversation’s analysis holds the AI evaluation (strengths, weaknesses, overall evaluation) and, for a custom agent, analytics holds its summary, extractions and scoring. recordingUrl, videoRecordingUrl and downloadUrl are signed links, valid until one hour after exportedAt. Download the files you need to hand over within that hour, or request a new export. A downloadUrl is null for a document whose file was never uploaded, and for the processed CV: its file is not kept after processing, and its text is in cvs.

Format version

formatVersion changes when a field is removed or changes meaning. Adding a field does not change it, so read the fields you know and ignore the rest.

Example

The example is shortened. The full shape of each section is in the response schema below.

What is not in the export

  • Deleted records. A conversation or contact you deleted is not exported. It is removed for good when its retention period ends.
  • Deletion archives. When a contact or a conversation is deleted, a snapshot of the record (name, e-mail, phone number) is kept in an internal archive for the configured retention period (30 days by default) and then removed. The archive is not reachable through the API, so it is not in the export. A contact that is still live has nothing in it.
  • Internal operational data. Billing reservations, call costs, provider call ids and similar records are about the call, not the person, and are left out.

Error Scenarios

  • 403 Forbidden: the API key lacks read:contacts or read:conversations.
  • 404 Not Found: no contact with that id belongs to your API key’s company. An id that exists nowhere and an id that belongs to another company answer identically, on purpose.

Erase Contacts by Identifier

Act on an erasure request

Contacts Resource Guide

Learn about managing contacts

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Path Parameters

id
string<uuid>
required

Contact to export.

Query Parameters

companyId
string

Required for ATS API keys to specify which company to access. Ignored for standard company API keys.

Response

Everything held about the contact.

formatVersion
string
required

Version of this export's format. Raised when a field is removed or changes meaning; adding a field does not raise it.

Example:

"1"

exportedAt
string<date-time>
required

When the export was made (UTC)

Example:

"2026-11-17T10:30:00.000Z"

contact
object
required

The contact as GET /contacts/{id} returns it, with its core fields and custom fields.

retiredFields
object
required

Custom field values still stored for the contact whose field has since been deleted from the company's catalog. contact.fields leaves them out, as GET /contacts/{id} does; they are personal data all the same. Empty object when there are none.

Example:
documents
object[]
required

The contact's documents as GET /contacts/{id}/documents lists them, each with a link to download its file.

cvs
object[]
required

Every CV processed for the contact, newest first, with the text read from it. The original file is not kept after processing, so the text is what is held.

conversations
object[]
required

Every conversation with the contact, oldest first, as GET /conversations/{id} returns it: call attempts with their transcripts and recording links, the analysis and, for a custom agent, its analytics. Recording links are signed and valid until one hour after exportedAt.

conversationTranscripts
object[]
required

Transcript segments that belong to no call attempt, as an online conversation records them, grouped by conversation. conversations carries transcripts per call attempt only.

questionAnalyses
object[]
required

The questions the analysis found in the contact's calls, with a summary of each answer.

callChecks
object[]
required

What the post-call check concluded about each call attempt.