---
title: "Update a single associated person"
method: PUT
path: "/associated_persons/{associatedPersonID}"
tags: ["Associated Persons"]
---

# Update a single associated person

`PUT /associated_persons/{associatedPersonID}`

## Request body

- AssociatedPerson
  - `first_name` string, required — The first name of the associated person
  - `middle_name` string — The middle name of the associated person
  - `last_name` string, required — The last name of the associated person
  - `transliterated_first_name` string — Required when the `first_name` includes any non Latin-1 characters. Acceptable characters - Latin-1 Unicode Character Range: À-ÖØ-ßà-öø-ÿ; Standard Unicode Character Range: -~
  - `transliterated_middle_name` string — Required when the `middle_name` includes any non Latin-1 characters. Acceptable characters - Latin-1 Unicode Character Range: À-ÖØ-ßà-öø-ÿ; Standard Unicode Character Range: -~
  - `transliterated_last_name` string — Required when the `last_name` includes any non Latin-1 characters. Acceptable characters - Latin-1 Unicode Character Range: À-ÖØ-ßà-öø-ÿ; Standard Unicode Character Range: -~
  - `email` string, required — The persons primary email address
  - `phone` string — The persons phone in format "+12223334444"
  - `residential_address` Address2025WinterRefresh, required
    - `street_line_1` string, required
    - `street_line_2` string
    - `city` string, required
    - `subdivision` string — ISO 3166-2 subdivision code. Must be supplied for US addresses.
    - `postal_code` string — Must be supplied for countries that use postal codes.
    - `country` string, required — Three-letter alpha-3 country code as defined in the ISO 3166-1 spec.
  - `transliterated_residential_address` Address2025WinterRefresh
    - `street_line_1` string, required
    - `street_line_2` string
    - `city` string, required
    - `subdivision` string — ISO 3166-2 subdivision code. Must be supplied for US addresses.
    - `postal_code` string — Must be supplied for countries that use postal codes.
    - `country` string, required — Three-letter alpha-3 country code as defined in the ISO 3166-1 spec.
  - `birth_date` string, required — Date of birth in format yyyy-mm-dd. Must be at least 18 years old.
  - `nationality` string — Legacy single nationality (ISO 3166-1 alpha-3). Prefer `nationalities` for all nationalities. See individual customer `nationality` / `nationalities` and [EEA nationalities](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#nationalities).
  - `nationalities` string[] — All nationalities for this associated person (ISO 3166-1 alpha-3). **EEA / BBSA in-scope businesses:** required on each UBO / associated person where policy applies.
  - `place_of_birth` PlaceOfBirthInput — Country (and optionally city) of birth. **EEA / BBSA in-scope customers:** supply when onboarding individuals or associated persons under the [EEA updated requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#country-of-birth-and-city-of-birth). This is a sparse address — no street address. At least `country` should be present when the object is sent; `city` is recommended and will be required by EU law in 2027.
    - `country` string — ISO 3166-1 alpha-3 country code for the place of birth.
    - `city` string — City of birth (recommended for EEA).
  - `verified_database_at` string, date-time — Write-only ISO 8601 timestamp. For **EEA in-scope** associated persons on **reliance**, second factor with `verified_govid_at` under `TWO_FORMS_OF_ID_RELIANCE`.
  - `has_ownership` boolean, required — True if this person has at least 25% ownership of the business.
  - `has_control` boolean, required — True if this is the control person of the company, having significant responsibility to control, manage or influence the activities of the business entity. At least one control person must be specified.
  - `is_signer` boolean, required — True if this person is able to authorize transactions on behalf of the business. At least one signer must be specified.
  - `is_director` boolean — True if this person is an appointed director of the company. **EEA / BBSA in-scope businesses:** must be set for every associated person (complete director list). See [EEA updated requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#complete-director-list).
  - `title` string — The title of this associated person at the company, e.g. CEO, CFO, etc. Required if has_control is true.
  - `ownership_percentage` integer — Ultimate ownership percentage of the business. **EEA / BBSA in-scope businesses:** required when `has_ownership` is true for UBOs at or above the configured threshold (default 25%). See [EEA updated requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#ownership-percentage-per-ubo).
  - `attested_ownership_structure_at` string — The date or timestamp when this individual attested to the correctness of the ownership structure provided to Bridge. If provided by at least one control person, ownership documents for the business are not required.
  - `verified_account_authorization_at` string, date-time — Write-only ISO 8601 timestamp. For **EEA in-scope** businesses on **reliance**, may satisfy signatory authority for signers who are not owner, director, or control person (`signature_authority_requirement(for_reliance: true)`); alternative is `documents` with purpose `proof_of_signatory_authority`. See [EEA updated requirements — LOA](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#letter-of-authority-loa).
  - `relationship_established_at` string — The date or timestamp when the associated person relationship was established in format yyyy-mm-dd.
  - `verified_govid_at` string, date-time — Write-only ISO 8601 timestamp. For **EEA in-scope** associated persons on **reliance**, use with `verified_selfie_at` or `verified_database_at` under `TWO_FORMS_OF_ID_RELIANCE`.
  - `verified_selfie_at` string, date-time — Write-only ISO 8601 timestamp. For **EEA in-scope** associated persons on **reliance**, pairs with `verified_govid_at` or `verified_database_at` under `TWO_FORMS_OF_ID_RELIANCE`.
  - `identifying_information` object[], required
    - `type` 'drivers_license' | 'matriculate_id' | 'military_id' | 'national_id' | 'passport' | 'permanent_residency_id' | 'state_or_provincial_id' | 'visa' | 'abn' | 'acn' | 'ahv' | 'ak' | 'aom' | 'arbn' | 'avs' | 'bc' | 'bce' | 'bin' | 'bir' | 'bp' | 'brn' | 'bsn' | 'bvn' | 'cc' | 'cdi' | 'cedula_juridica' | 'cf' | 'cif' | 'cin' | 'cipc' | 'cn' | 'cnp' | 'cnpj' | 'cpf' | 'cpr' | 'crc' | 'crib' | 'crn' | 'cro' | 'cui' | 'cuil' | 'curp' | 'cuit' | 'cvr' | 'edrpou' | 'ein' | 'embg' | 'emirates_id' | 'en' | 'fin' | 'fn' | 'gstin' | 'gui' | 'hetu' | 'hkid' | 'hn' | 'ic' | 'ico' | 'id' | 'id_broj' | 'idno' | 'idnp' | 'idnr' | 'if' | 'iin' | 'ik' | 'inn' | 'ird' | 'itin' | 'itr' | 'iva' | 'jmbg' | 'kbo' | 'kvk' | 'matricule' | 'mf' | 'mn' | 'ms' | 'mst' | 'nic' | 'nicn' | 'nie' | 'nif' | 'nin' | 'nino' | 'nip' | 'nipc' | 'nipt' | 'nit' | 'npwp' | 'nric' | 'nrn' | 'nrt' | 'ntn' | 'nuit' | 'nzbn' | 'oib' | 'orgnr' | 'other' | 'pan' | 'partita_iva' | 'pesel' | 'pib' | 'pin' | 'pk' | 'ppsn' | 'qid' | 'rc' | 'regon' | 'rfc' | 'ricn' | 'rif' | 'rn' | 'rnc' | 'rnokpp' | 'rp' | 'rrn' | 'rtn' | 'ruc' | 'rut' | 'si' | 'sin' | 'siren' | 'siret' | 'spi' | 'ssm' | 'ssn' | 'steuer_id' | 'strn' | 'tckn' | 'tfn' | 'tin' | 'tpin' | 'trn' | 'ucn' | 'uen' | 'uic' | 'uid' | 'usc' | 'ust_idnr' | 'utr' | 'vat' | 'vkn' | 'voen' | 'y_tunnus', required — Tax identification number type or government-issued ID document type (see enum). Country-specific tax and national ID lists: [Individuals](https://apidocs.bridge.xyz/docs/individual-tax-identification-numbers-by-country), [Businesses](https://apidocs.bridge.xyz/docs/business-tax-identification-numbers-by-country). **EEA / BBSA (policy in `eea_requirements.rb`):** In-scope individuals and UBOs need **both** a valid national-ID-type entry and a valid TIN per [EEA updated requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements). In-scope businesses need business registration **and** business tax ID types per country tables there. **TIN issuing country** must match residence (individuals) or incorporation (businesses). **Foreign tax** outside the incorporation country: set `has_foreign_tax_registration` on the business customer and add TIN objects per jurisdiction ([foreign tax / tax residency](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements#tax-residency-status-foreign-tax-registry)).
    - `issuing_country` string, required — The ISO 3166-1 (three-character) country code that issued the provided document.
    - `number` string — The unique identifier of the document. Required if this document is being used as a tax identification number (e.g., you are providing a passport or national_id with no other identification).
    - `description` string — A description describing the provided document. This field is required when `other` is selected.
    - `expiration` string — The expiration date of the given document in yyyy-mm-dd format.
    - `image_front` string — This field is optionally accepted for tax_id types, but required for government_id types. Base64 encoded image* of the front side of the provided document, following the data-uri scheme i.e. data:image/[type];base64,[base_64_encoded_file_contents], with a minimum size of 200px x 200px \n\n*Maximum File Size: 15MB\n\n*Valid file types: .pdf, .jpeg, .jpg, .png, .heic, .tif _Note: When combined with an `image_back`, the combined size of both images must not exceed 24MB._
    - `image_back` string — Base64 encoded image* of the back side of the provided document, following the data-uri scheme i.e. data:image/[type];base64,[base_64_encoded_file_contents], with a minimum size of 200px x 200px \n\n*Maximum File Size: 15MB\n\n*Valid file types: .pdf, .jpeg, .jpg, .png, .heic, .tif _Note: When combined with an `image_front`, the combined size of both images must not exceed 24MB._
  - `documents` object[] — Please click "ADD OBJECT" for more information.
    - `purposes` string[], required — A list of purposes that the given document serves. Click "ADD STRING" to see common document purposes for individuals, or view the full list of possible values [here](https://apidocs.bridge.xyz/docs/supported-documents).
    - `file` string, required — Base64 encoded image* of the provided document, following the data-uri scheme i.e. data:image/[type];base64,[base_64_encoded_file_contents], with a minimum size of 200px x 200px *Maximum File Size: 24MB *Valid file types: .pdf, .jpeg, .jpg, .png, .heic, .tif
    - `description` string — A description describing the provided document. This field is required when `other` is provided as one of the purposes.

## Response `200`

Updated associated person

- AssociatedPersonResponse
  - `id` string, required — Unique identifier for the associated person
  - `email` string — The email address of the associated person
  - `first_name` string — The first name of the associated person
  - `last_name` string — The last name of the associated person
  - `has_ownership` boolean — True if this person has at least 25% ownership of the business.
  - `has_control` boolean — True if this is the control person of the company, having significant responsibility to control, manage or influence the activities of the business entity.
  - `is_signer` boolean — True if this person is able to authorize transactions on behalf of the business.
  - `title` string — The title of this associated person at the company, e.g. CEO, CFO, etc.
  - `attested_ownership_structure_at` string — When this individual attested to the correctness of the ownership structure provided to Bridge. If provided by at least one control person, ownership documents for the business are not required.
  - `relationship_established_at` string — When the associated person relationship was established in format yyyy-mm-dd.
  - `created_at` integer, required — Created timestamp in milliseconds since Unix epoch
  - `updated_at` integer, required — Last updated timestamp in milliseconds since Unix epoch

## Other responses

- `400` — Request containing missing or invalid parameters.
- `401` — Missing or invalid API key
- `404` — No resource found
- `500` — Unexpected error. User may try and send the request again.

---

[API](https://skmtc.net/bridge/apis/bridge-api.md) · [All operations](https://skmtc.net/bridge/apis/bridge-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bridge/bridge-api/revisions/570998bde3b5/schema)