---
title: "Erase a person (GDPR)"
method: POST
path: "/api/v1/subscribers/{email}/erase"
tags: ["Subscribers"]
---

# Erase a person (GDPR)

`POST /api/v1/subscribers/{email}/erase`

## Request

- Base URL: `https://mailcheer.com`
- URL: `https://mailcheer.com/api/v1/subscribers/{email}/erase`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Api-Key`

Permission required: `subscribers:write`. **Irreversible.**

The right to erasure: the record, the name, the custom fields, the proof of consent and the tags are deleted. What was promised and not sent will not be sent; automation journeys stop. The statistics of campaigns already sent do not move — each message stays counted, with nothing left that links it to the person.

Distinct from `DELETE /api/v1/subscribers/{email}`, which unsubscribes and KEEPS the record so the address does not come back at the next import. The suppression list is not touched: an address on it stays there (`suppressed: true`), which is what guarantees nothing is sent to it again. Removing an address from that list is done by hand, in the workspace.

## Path parameters

- `email` string, email, required

## Response `200`

Erased.

- SubscriberErasure
  - `object` 'subscriber'
  - `email` string
  - `erased` true
  - `suppressed` boolean: `true` if the address stays on the suppression list — nothing will be sent to it again, even re-imported.

## Other responses

- `401`: Key missing, unknown or revoked.
- `403`: The key does not have the requested permission, or the workspace cannot send: `sending_blocked` (suspended, blocked or banned — nothing goes out, through any channel), `commitment_required` (the anti-spam commitment is not accepted), `reputation_blocked` (too many bounces or complaints).
- `404`: The object does not exist in this workspace.

---

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