Skip to main content
PATCH
Rename or activate/deactivate a contact document
Renames a contact document and/or controls whether agents may use it.

Overview

Send title, isActive, or both. An empty body is a 400. Deactivating keeps the document but stops it being attached to new calls. It is also the way to keep a contact’s CV out of calls while keeping the CV itself: set isActive: false on the document whose source is CV. Nothing about the contact’s processing changes; the agent simply no longer has the document to look up. The CV document cannot be renamed — its title is set by the platform and would be reset the next time the CV was synced. Only completed (READY) documents can be toggled; a PENDING upload is a 409.

Example

Error Scenarios

  • 400 Bad Request: Neither title nor isActive was provided
  • 404 Not Found: No such document on that contact
  • 409 Conflict: The upload has not been completed yet, or the request renames the CV document

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Path Parameters

id
string<uuid>
required

Contact the document belongs to.

documentId
string<uuid>
required

Document id.

Query Parameters

companyId
string

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

Body

application/json
title
string

New human-readable label for the document. Not accepted for the CV document, whose title is set by the platform.

Maximum string length: 255
Example:

"Cover letter (2026)"

isActive
boolean

Whether agents may consult this document during a call. Deactivating keeps the document — it simply stops being attached to new calls. Only READY documents can be toggled.

Example:

false

Response

Document updated

id
string<uuid>
required

Document ID

Example:

"123e4567-e89b-12d3-a456-426614174000"

title
string
required

Human-readable label for the document

Example:

"Benefits and perks"

status
enum<string>
required

PENDING while waiting for the file to be uploaded to the presigned URL and the upload to be completed; READY once the file is confirmed stored. Only READY documents are attached to calls.

Available options:
PENDING,
READY
Example:

"READY"

isActive
boolean
required

Whether the agent may consult this document during a call. Always false while the upload is PENDING.

Example:

true

source
enum<string>
required

UPLOAD for a file attached through the API or the dashboard. CV for the document the platform produces from a contact's processed CV (contacts only); a CV document can be deactivated but not renamed or deleted. Always UPLOAD on an agent's knowledge base.

Available options:
UPLOAD,
CV
Example:

"UPLOAD"

createdAt
string<date-time>
required

When the document was created

Example:

"2026-08-08T10:15:00.000Z"

fileName
string

Original file name as uploaded

Example:

"benefits-and-perks.pdf"

mimeType
string

MIME type of the stored file

Example:

"application/pdf"

sizeBytes
number

Size of the stored file in bytes, as verified against storage. Absent until the upload is READY.

Example:

482133