---
title: "Purge personal data (PII) from a verification"
method: POST
path: "/verification/{verificationId}/purgePersonData"
tags: ["verification"]
---

# Purge personal data (PII) from a verification

`POST /verification/{verificationId}/purgePersonData`

Submit a request to purge the personal data (PII) from the provided verification, and expire it if it isn't already.
Requires an API token. User must have "Account Owner" or "Customer Service Manager" role, and must be a member of the account that the verification belongs to.
The purge and expire operations are asynchronous; in most cases it will be completed within 5 minutes.

## Path parameters

- `verificationId` string, required

## Response `200`

The purge request has been accepted.

- object — Empty object (properties may be added in the future)

## Other responses

- `401` — Unauthorized
- `404` — Verification not found
- `429` — Too many requests. A `429` can mean one of two things — inspect the response body's `errorIds` before retrying: - A transient rate limit applied at the platform edge. If a `Retry-After` header is present, wait that many seconds (using exponential backoff) and retry. - A program/consumer limit such as `verificationLimitExceeded`, `reverificationDailyLimitExceeded`, or `docReviewLimitExceeded` — the consumer has exhausted an allowance defined by the program's limiting policy. This is a permanent rejection (`currentStep: error`, no `Retry-After`); do not retry.
- `500` — Internal server error.
- `503` — Service temporarily unavailable. The request can be safely retried after the interval given in the `Retry-After` header.

---

[API](https://skmtc.dev/sheerid/apis/sheerid-api.md) · [All operations](https://skmtc.dev/sheerid/apis/sheerid-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sheerid/sheerid-api/revisions/dc7f4e84f543/schema)