Skip to main content
DELETE
Delete a contact document
Permanently deletes an uploaded contact document, its stored file and the copy held by the voice provider.

Overview

Works on UPLOAD documents, completed or not — deleting a PENDING upload releases its slot and its bytes immediately instead of waiting for the 24-hour cleanup. The CV document is refused with a 409. It is produced from the contact’s processed CV, so deleting the document would only have it listed again on the next read. To keep the CV out of calls, deactivate it; to remove it entirely, delete the contact’s CV.
Contact documents follow the contact’s retention. When a contact reaches its GDPR expiry date, every document on it — the CV projection and the uploads, their stored files and their provider copies — is deleted with the rest of the contact’s data. There is no second retention clock to manage.

Example

Error Scenarios

  • 404 Not Found: No such document on that contact
  • 409 Conflict: The document is the contact’s CV

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.

Response

Deleted successfully

id
string<uuid>
required

Id of the deleted resource

deleted
enum<boolean>
required

Always true; a failed delete answers with an error status

Available options:
true
Example:

true