Associated Persons

Bridge's /associated_persons resource. Beneficial owners, controllers, signers, and directors attached to a business customer.

The most common case, seeding them at onboarding, is covered by the associated_persons[] array in the business customer create body. The endpoints here are for post-onboarding lifecycle: adding a new owner, updating a title, removing someone who left.

The AssociatedPerson schema (all field definitions, enums, and nested sub-objects) lives under Shared schemas.

Endpoints

• GET /associated_persons/{id}: fetch by id, no customer id required.
• PUT /associated_persons/{id}: partial update.
• DELETE /associated_persons/{id}: soft-delete.
• POST /customers/{id}/associated_persons: add a new person to an existing business customer.
• GET /customers/{id}/associated_persons: list all persons on a customer.

Nested path aliases

Bridge also exposes the single-person endpoints scoped under the parent customer. These are exact aliases of the flat variants, with the same behavior and response:

• GET /customers/{customer-id}/associated_persons/{id} → GET /associated_persons/{id}
• PUT /customers/{customer-id}/associated_persons/{id} → PUT /associated_persons/{id}
• DELETE /customers/{customer-id}/associated_persons/{id} → DELETE /associated_persons/{id}

If {customer-id} in the path doesn't match the person's actual customer_id, we return 404, same as Bridge.