Update a person relation on a business customer

PATCH 
/v1/customers/business/:businessUserId/related-persons

Updates an existing person relation (ownership percentage, representing range) for a business customer.

The person relation is identified by userId + role in the request body. Use ownershipPercentage to change ownership and representingRange to update the beneficial ownership period.

Pre-approval (PENDING status): Updates the onboarding data. Post-approval (APPROVED status): Updates the beneficial owner record via banking partner integration.

Same hard constraints validated as the add endpoint.

Request

Path Parameters

businessUserId stringrequired

The ID of the business customer

application/json

Body

required

Updated person relation details

relation

object

required

userId stringrequired

User ID of the related person

role stringrequired

Possible values: [REPRESENTATIVE, SHAREHOLDER]

Current role — identifies which relationship to update

ownershipPercentage string

New ownership percentage as a string (required when target role is SHAREHOLDER, e.g. "51", "30.5")

representingRange

object

Representing date range (omit to keep current)

startDate stringrequired

Start date of the representing period (ISO 8601)

endDate string

End date (ISO 8601, omit for open-ended)

Responses

200

The person relation was successfully updated.

application/json

Schema

Schema

traceId string
message string

data

object

personRelations

object[]

required

Updated list of person relations

Array [

userId stringrequired

User ID of the related person

role stringrequired

Role of the person in the business

ownershipPercentage string

Ownership percentage (present for SHAREHOLDER role)

]

action stringrequired

Possible values: [ADD, UPDATE, REMOVE]

Action that was performed

Example (from schema)

{
  "traceId": "string",
  "message": "string",
  "data": {
    "personRelations": [
      {
        "userId": "123e4567-e89b-12d3-a456-426614174021",
        "role": "SHAREHOLDER",
        "ownershipPercentage": "51"
      }
    ],
    "action": "ADD"
  }
}

400

Invalid request payload. This can happen if required fields are missing or have invalid formats.

application/json

Schema

Schema

traceId string
message string

Example (from schema)

{
  "traceId": "string",
  "message": "string"
}

403

The API key is invalid or the client does not have sufficient permissions.

application/json

Schema

Schema

traceId string
message string

Example (from schema)

{
  "traceId": "string",
  "message": "string"
}

404

One of the specified resources was not found. Does not apply for empty result set.

application/json

Schema

Schema

traceId string
message string

Example (from schema)

{
  "traceId": "string",
  "message": "string"
}

Loading...