Update Legal Entity

Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

Update a legal_entity. Updates are partial—send only the fields you want to change, so every field below is optional. The fields available depend on the entity's legal_entity_type (which cannot be changed). This page consolidates the fields, formats, and requirements you need to build a valid request; see the linked pages for edge cases.

📘
Name Updates
Name attributes can only be updated for legal entities that have a status of pending or denied.

Updatable fields for individuals

Field	Type	Notes
first_name	string	Legal first name. Name updates are restricted to `pending`/`denied` entities.
last_name	string	Legal last name. Name updates are restricted to `pending`/`denied` entities.
date_of_birth	string	Format: `YYYY-MM-DD`.
email	string	Primary email address.
phone_numbers	array object	Each `phone_number` is in E.164 format, e.g. `+12061111111`.
addresses	array object	See Address fields.
identifications	array object	See Identification fields.

Updatable fields for businesses

Field	Type	Notes
business_name	string	Legal business name. Name updates are restricted to `pending`/`denied` entities.
date_formed	string	Formation date. Format: `YYYY-MM-DD`.
legal_structure	string	One of `corporation`, `llc`, `non_profit`, `partnership`, `sole_proprietorship`, `trust`.
business_description	string	A description of the business.
intended_use	string	A description of the intended use of the business.
expected_activity_volume	number	Monthly expected transaction volume in USD dollars.
country_of_incorporation	string	Country code conforms to ISO 3166-1 alpha-2 (e.g. `US`).
addresses	array object	See Address fields. `address_types` is required for businesses.
identifications	array object	See Identification fields.

Address fields

If you include addresses, each entry requires line1, locality, region, postal_code, and country. country conforms to ISO 3166-1 alpha-2 (e.g. US). Businesses must also set address_types (e.g. ["business"], ["business_registered"]).

Identification fields

If you include identifications, each entry requires id_number and id_type. Include issuing_country (ISO 3166-1 alpha-2) unless the id_type already encodes the country (the first two letters of id_type are the ISO country code). For the full list of supported id_type values and their formats, see Identifications.

📘
Country-specific ID requirements and identification-document rules are covered in Onboard an Individual and Onboard a Business.

📘
Attaching New Documents
To attach new documents to a legal entity utilize the POST /documents endpoint, passing in the legal entity's id as the documentable_id.

Example requests

{
  "email": "[email protected]",
  "phone_numbers": [
    { "phone_number": "+12125550100" }
  ],
  "addresses": [
    {
      "address_types": ["residential"],
      "line1": "123 Main Street",
      "locality": "New York",
      "region": "NY",
      "postal_code": "10001",
      "country": "US"
    }
  ]
}

{
  "business_description": "Software development and consulting services.",
  "country_of_incorporation": "US",
  "addresses": [
    {
      "address_types": ["business"],
      "line1": "500 Market Street",
      "line2": "Suite 400",
      "locality": "San Francisco",
      "region": "CA",
      "postal_code": "94105",
      "country": "US"
    }
  ],
  "identifications": [
    {
      "id_number": "451234567",
      "id_type": "us_ein",
      "issuing_country": "US"
    }
  ]
}

For more sample payloads, see Example Requests.