> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inflection.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Erasure API Endpoint

> Initiate a user data erasure request based on the user's email address.

## Overview

This document describes the usage of the `Erasure API` endpoint provided by Inflection.io. This endpoint is used to initiate a user data erasure request based on the user's email address.

## Endpoint

```text theme={null}
POST https://core-integrations.inflection.io/v1/erasure/persons
```

## Authentication

The endpoint requires Bearer token authentication. The token must be passed in the `Authorization` header.

**Header Example:**

```text theme={null}
Authorization: Bearer <your_access_token>
```

<Info>
  The endpoint URL and Bearer Token for your workspace are shown when you create a Custom DSR connection — see [Data Subject Erasure Requests](/settings/data-subject-erasure-requests).
</Info>

## Request

### Headers

```json theme={null}
{
  "Authorization": "Bearer <your_access_token>",
  "Content-Type": "application/json"
}
```

### Body Parameters

| Field | Type   | Description                |
| ----- | ------ | -------------------------- |
| email | string | Email address to be erased |

**Sample Request Body:**

```json theme={null}
{
  "email": "3ho3fvi0uz@example.com"
}
```

## Sample `curl` Command

```shell theme={null}
curl --location 'https://core-integrations.inflection.io/v1/erasure/persons' \
--header 'Authorization: Bearer <your_access_token>' \
--header 'Content-Type: application/json' \
--data-raw '{
  "email": "3ho3fvi0uz@example.com"
}'
```

## Responses

### Success - Request Initiated

```json theme={null}
{
  "data": {
    "status": "SUCCESS",
    "message": "Erasure request successfully initiated.",
    "requestId": "688123748f37ed1cd3a148fb"
  },
  "meta": {
    "status": "SUCCESS",
    "timestamp": "2025-07-23T18:01:25.635Z"
  }
}
```

### Success - Request Already Exists

```json theme={null}
{
  "data": {
    "status": "SUCCESS",
    "message": "Request Already Exists",
    "requestId": "688123748f37ed1cd3a148fb"
  },
  "meta": {
    "status": "SUCCESS",
    "timestamp": "2025-07-23T18:02:02.502Z"
  }
}
```

## Notes

* The `requestId` can be used for tracking or auditing the status of the erasure request.
* The endpoint is idempotent. If a request for the same email has already been initiated, it will return the same `requestId` with the message `"Request Already Exists"`.