Skip to main content
PUT
Update beneficiary

Authorizations

Authorization
string
header
required

Enter Auth0 JWT token

Headers

Zuba-Account-Id
string<uuid>

Optional. Names an owned sub-account (UUID) to act on. Omit to act at the master (tenant) level. Naming an account this key does not own returns 403 not_account_owner.

Path Parameters

id
string<uuid>
required

Unique identifier for the beneficiary

Example:

"123e4567-e89b-12d3-a456-426614174000"

Body

application/json
address
string

Address line 1 of the beneficiary (max 200 characters)

Maximum string length: 200
Example:

"Hauptstraße 123"

addressLine2
string

Address line 2 of the beneficiary (max 200 characters)

Maximum string length: 200
Example:

"Apt 4B, 3rd Floor"

city
string

City of the beneficiary

Maximum string length: 100
Example:

"Berlin"

countrySubdivision
string

Country subdivision code (e.g., US state code "NY", "CA")

Maximum string length: 50
Example:

"NY"

dateOfBirth
string

Date of birth in YYYY-MM-DD format (individual beneficiaries only). Use this to add one to a saved individual beneficiary before sending a crypto payout while Travel Rule screening is enabled.

Example:

"1985-05-20"

email
string<email>

Email address of the beneficiary

Example:

"john.doe@example.com"

middleName
string

Middle name of the beneficiary (max 100 characters)

Maximum string length: 100
Example:

"James"

name
string

Full name of the beneficiary (2-100 characters)

Required string length: 2 - 100
Example:

"John Doe"

notes
string

Notes about the beneficiary (max 500 characters)

Maximum string length: 500
Example:

"Regular client, prefers SEPA Instant"

postcode
string

Postal code of the beneficiary

Maximum string length: 20
Example:

"10115"

status
enum<string>

Beneficiary status. inactive is not settable here — deleting a beneficiary goes through DELETE /v1/beneficiaries/{id}, which refuses while a payout or order against it is still live.

Available options:
active,
suspended
Example:

"active"

type
enum<string>

Beneficiary type

Available options:
individual,
business
Example:

"individual"

Response

Beneficiary updated successfully

accounts
object[]
required

Array of associated payment accounts

country
string
required

Country code (ISO 3166-1 alpha-2)

Example:

"DE"

createdAt
string<date-time>
required

ISO timestamp when the beneficiary was created

Example:

"2024-01-15T10:30:00Z"

id
string<uuid>
required

Unique identifier for the beneficiary

Example:

"123e4567-e89b-12d3-a456-426614174000"

name
string
required

Full name of the beneficiary

Example:

"John Doe"

status
enum<string>
required

Beneficiary status

Available options:
active,
inactive,
suspended
Example:

"active"

type
enum<string>
required

Beneficiary type

Available options:
individual,
business
Example:

"individual"

updatedAt
string<date-time>
required

ISO timestamp when the beneficiary was last updated

Example:

"2024-01-15T10:30:00Z"

accountId
string<uuid>

The sub-account this beneficiary belongs to. Absent on the workspace’s own. A headerless list is a rollup over both, so this is what tells them apart.

address
string

Address line 1 of the beneficiary

Example:

"Hauptstraße 123"

addressLine2
string

Address line 2 of the beneficiary

Example:

"Apt 4B, 3rd Floor"

city
string

City of the beneficiary

Example:

"Berlin"

countrySubdivision
string

Country subdivision code (e.g., US state code "NY", "CA")

Example:

"NY"

dateOfBirth
string

Date of birth in YYYY-MM-DD format (individual beneficiaries only).

Example:

"1985-05-20"

email
string

Email address of the beneficiary

Example:

"john.doe@example.com"

middleName
string

Middle name of the beneficiary

Example:

"James"

notes
string

Notes about the beneficiary

Example:

"Regular client, prefers SEPA Instant"

postcode
string

Postal code of the beneficiary

Example:

"10115"