---
title: "Re-identify redacted values."
method: POST
path: "/api/reidentify"
tags: ["Re-identification"]
---

# Re-identify redacted values.

`POST /api/reidentify`

Reverses one or more values that were redacted via the CRYPTO_REPLACE or FPE_ENCRYPT_REPLACE strategy. The caller must supply a stated reason, which is recorded in the audit log alongside the actor, timestamp, and count of reversals. A user may re-identify their own values; an admin may re-identify any user's values by supplying that user's email via the owner parameter. CRYPTO_REPLACE requires policyName so the key can be resolved from the stored policy. FPE_ENCRYPT_REPLACE uses the user's per-account FPE key; if the policy specified a custom FPE key, also pass policyName so that key is used instead. Requires the `reidentify` scope.

## Query parameters

- `owner` string

## Headers

- `Authorization` string, required

## Request body

- ReidentifyRequest
  - `policyName` string
  - `reason` string
  - `strategy` string
  - `values` string[]

## Response `200`

Request processed; inspect each result for per-value errors.

## Other responses

- `400` — Missing or invalid request fields.
- `401` — Missing or invalid API key.
- `404` — Named policy not found, or owner not found.
- `413` — Content Too Large
- `415` — Unsupported Media Type
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/philterd/apis/philter-api.md) · [All operations](https://skmtc.net/philterd/apis/philter-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/philterd/philter-api/versions/67443cd5a65b/schema)