---
title: "Create a new beneficial owner individual or replace the existing control person entity"
method: POST
path: "/v1/account_holders/{account_holder_token}/entities"
tags: ["Account Holder"]
---

# Create a new beneficial owner individual or replace the existing control person entity

`POST /v1/account_holders/{account_holder_token}/entities`

Create a new beneficial owner individual or replace the control person entity on an existing KYB account holder. This endpoint is only applicable for account holders enrolled through a KYB workflow with the Persona KYB provider.
A new control person can only replace the existing one. A maximum of 4 beneficial owners can be associated with an account holder.

## Path parameters

- `account_holder_token` string, uuid, required

## Request body

- CreateEntityRequest — Request body for creating a new beneficial owner or replacing the control person entity on an existing KYB account holder.
  - `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.
  - `dob` string, required — Individual's date of birth, as an RFC 3339 date.
  - `email` string, required — Individual's email address. If utilizing Lithic for chargeback processing, this customer email address may be used to communicate dispute status and resolution.
  - `first_name` string, required — Individual's first name, as it appears on government-issued identity documents.
  - `last_name` string, required — Individual's last name, as it appears on government-issued identity documents.
  - `phone_number` string, required — Individual's phone number, entered in E.164 format.
  - `government_id` string, required — Government-issued identification number (required for identity verification and compliance with banking regulations). Social Security Numbers (SSN) and Individual Taxpayer Identification Numbers (ITIN) are currently supported, entered as full nine-digits, with or without hyphens
  - `type` 'BENEFICIAL_OWNER_INDIVIDUAL' | 'CONTROL_PERSON', required — The type of entity associated with an account holder

## Response `200`

OK

- CreateEntityResponse — Response body for creating a new beneficial owner or replacing the control person entity on an existing KYB account holder.
  - `account_holder_token` string, uuid, required — Globally unique identifier for the account holder
  - `created` string, date-time, required — Timestamp of when the entity was created
  - `status` 'ACCEPTED' | 'INACTIVE' | 'PENDING_REVIEW' | 'REJECTED', required — The status of an entity associated with an account holder
  - `status_reasons` StatusReasons[], required — Reason for the evaluation status
  - `required_documents` RequiredDocument[], required — A list of documents required for the entity to be approved
    - `entity_token` string, uuid, required — Globally unique identifier for an entity.
    - `valid_documents` string[], required — A list of valid documents that will satisfy the KYC requirements for the specified entity.
    - `status_reasons` string[], required — Provides the status reasons that will be satisfied by providing one of the valid documents.
  - `token` string, uuid, required — Globally unique identifier for the entity

## Other responses

- `400` — A parameter in the query given in the request does not match the valid queries for the endpoint.
- `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.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)