---
title: "Deactivate a beneficial owner individual"
method: DELETE
path: "/v1/account_holders/{account_holder_token}/entities/{entity_token}"
tags: ["Account Holder"]
---

# Deactivate a beneficial owner individual

`DELETE /v1/account_holders/{account_holder_token}/entities/{entity_token}`

Deactivate a beneficial owner individual on an existing KYB account holder. Only beneficial owner individuals can be deactivated.

## Path parameters

- `account_holder_token` string, uuid, required
- `entity_token` string, uuid, required

## Response `200`

OK

- EntityResponse — Information about an entity associated with an account holder
  - `account_holder_token` string, uuid, required — Globally unique identifier for the account holder
  - `token` string, uuid, required — Globally unique identifier for the entity
  - `type` 'BENEFICIAL_OWNER_INDIVIDUAL' | 'CONTROL_PERSON', required — The type of entity associated with an account holder
  - `status` 'ACCEPTED' | 'INACTIVE' | 'PENDING_REVIEW' | 'REJECTED', required — The status of an entity associated with an account holder
  - `first_name` string, nullable, required — Individual's first name, as it appears on government-issued identity documents
  - `last_name` string, nullable, required — Individual's last name, as it appears on government-issued identity documents
  - `email` string, nullable, required — Individual's email address
  - `phone_number` string, nullable, required — Individual's phone number, entered in E.164 format
  - `dob` string, nullable, required — Individual's date of birth, as an RFC 3339 date
  - `address` Address, required
    - `address1` string, required — Valid deliverable address (no PO boxes).
    - `address2` string — Unit or apartment number (if applicable).
    - `city` string, required — Name of city.
    - `country` string, required — Valid country code. Only USA is currently supported, entered in uppercase ISO 3166-1 alpha-3 three-character format.
    - `postal_code` string, required — Valid postal code. Only USA ZIP codes are currently supported, entered as a five-digit ZIP or nine-digit ZIP+4.
    - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format.

## Other responses

- `401` — | | | |---|---| | User has not been authenticated | Invalid or missing API key | | API key is not active | The API key used is no longer active | | Could not find API key | The API key provided is not associated with any user | | Please provide API key in Authorization header | The Authorization header is not in the request | | Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](https://lithic.com/contact) | | Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege | Reach out at [lithic.com/contact](https://lithic.com/contact) |
- `404` — The specified resource was not found.
- `422` — Unprocessable entity.
- `429` — Client has exceeded the number of allowed requests in a given time period. | | | |---|---| | Rate limited, too many requests per second | User has exceeded their per second rate limit | | Rate limited, reached daily limit | User has exceeded their daily rate limit | | Rate limited, too many keys tried | One IP has queried too many different API keys |

---

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