---
title: "Delete Purposes from Data Subjects"
method: DELETE
path: "/rest/api/consent/v4/data-subjects/profiles"
tags: ["Data Subjects V4"]
---

# Delete Purposes from Data Subjects

`DELETE /rest/api/consent/v4/data-subjects/profiles`

Initiates TTL-based deletion of specific purposes from data subjects

## Request body

- ConsentAPIDeletePurposeFromDataSubjectV4
  - `purposes` string[], required — The unique identifiers of the purposes.
  - `identifier` string, required — The data subject identifier of the data subject.
  - `retainReceipts` boolean — This flag indicates whether receipts will be retained while deleting purposes from data subjects. When set to `false`, receipts are removed from the database and no longer appear in the OneTrust Platform UI. However, these receipts are not permanently deleted and can still be retrieved using the [Get List of Receipts API](https://developer.onetrust.com/onetrust/reference/getreceiptlistdetailsusingpost).

## Response `200`

Accepted request to delete purposes from DataSubjects using TTL

- string

## Other responses

- `400` — Bad Request
- `401` — Unauthorized access
- `403` — Forbidden
- `404` — Unable to find a datasubject with given identifier
- `422` — Missing identifier(or)additionalidentifier OR missing purposes in the request
- `429` — Too Many Requests. For more information, see [API Rate Limits](https://developer.onetrust.com/onetrust/reference/rate-limits-overview).
- `500` — Internal Server Error

---

[API](https://skmtc.net/onetrust/apis/platform-access-management.md) · [All operations](https://skmtc.net/onetrust/apis/platform-access-management/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/onetrust/platform-access-management/versions/21de3aa0b170/schema)