---
title: "Full Delete Contact"
method: POST
path: "/v2/full-delete"
---

# Full Delete Contact

`POST /v2/full-delete`

## Request

- Base URL: `https://pub-api.conversion.ai/api`
- URL: `https://pub-api.conversion.ai/api/v2/full-delete`
- Auth: one of:
  - API key in header `X-API-Key`
  - API key in query parameter `api_key`

Permanently delete a contact and suppress its identifiers for GDPR and CCPA erasure requests.

Identify the contact with `email`, `cnvContactId`, or `userId`. At least one is required.

A full delete removes the contact's personal data and engagement data as described in [Data deletion](/product-docs/gdpr/data-deletion), then suppresses the provided identifiers so the contact is not re-created.

Deletion is permanent and cannot be reversed.

> **Request access.** This endpoint is not enabled by default, contact the Conversion team to request access. Calls from accounts without it return `403 export_not_enabled`.

## Request body

- object
  - `email` string, email: The contact's email address. At least one of `email`, `cnvContactId`, or `userId` is required.
  - `cnvContactId` string, uuid: The Conversion contact ID. At least one of `email`, `cnvContactId`, or `userId` is required.
  - `userId` string: The external user identifier for the contact, as passed to the Events endpoints. At least one of `email`, `cnvContactId`, or `userId` is required.

## Response `204`

The contact was deleted and its identifiers suppressed. The response has no body.

## Other responses

- `400`: The request was malformed or contained invalid data.
- `401`: Authentication failed.
- `403`: The full delete API is not enabled for this account.
- `500`: An unexpected server error occurred.

---

[API](https://skmtc.dev/conversion/apis/conversion-api.md) - [All operations](https://skmtc.dev/conversion/apis/conversion-api/llms.txt) - [OpenAPI document](https://skmtc.dev/conversion/apis/conversion-api/revisions/8422f815402a?raw)