Update Client
PUT/v1/crossborder/clients/:id
Update an existing crossborder client. Only provided fields will be updated.
Request
Path Parameters
Client ID.
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
The product ID is a UUID (v4) used to identify the Z.ro product configuration.
The product target user ID is a UUID (v4) used to identify what user account this request must be executed. Require: x-product-uuid.
- application/json
Body
required
Client name.
Possible values: [NATURAL_PERSON, LEGAL_PERSON]
Client type.
Possible values: [US, BR, MX, AR, CO, CL, PE, EC, UY, PY]
Country code.
Nationality.
Document number.
Possible values: [CPF, CNPJ, DNI, PASSPORT, RUT, RUC, CUIL, CUIT, RFC, CURP, CE, PAS, PP]
Document type.
Email address.
Birth date.
Issue date.
address object
Street line 1.
Street line 2.
City.
State.
Subdivision.
Postal code.
Possible values: [US, BR, MX, AR, CO, CL, PE, EC, UY, PY]
Country.
Responses
- 200
- 400
- 401
- 422
Client updated successfully.
- application/json
- Schema
- Example (from schema)
Schema
Client ID.
Client name.
Possible values: [NATURAL_PERSON, LEGAL_PERSON]
Client type.
Possible values: [US, BR, MX, AR, CO, CL, PE, EC, UY, PY]
Country code.
Nationality.
Document number.
Possible values: [CPF, CNPJ, DNI, PASSPORT, RUT, RUC, CUIL, CUIT, RFC, CURP, CE, PAS, PP]
Document type.
Email address.
Birth date.
Issue date.
address objectrequired
Address ID.
Street line 1.
Street line 2.
City.
State.
Subdivision.
Postal code.
Possible values: [US, BR, MX, AR, CO, CL, PE, EC, UY, PY]
Country.
Possible values: [ACTIVE, INACTIVE, PENDING]
Client status.
Client created date.
Client updated date.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"name": "John Doe",
"type": "NATURAL_PERSON",
"country": "US",
"nationality": "American",
"document": "12345678901",
"document_type": "CPF",
"email": "john.doe@example.com",
"birth_date": "1990-01-01",
"issue_date": "2020-01-01",
"address": {
"id": "8fc58500-b12e-49d7-892c-dfd704b94c2d",
"street_line_1": "123 Main Street",
"street_line_2": "Suite 500",
"city": "San Francisco",
"state": "CA",
"subdivision": "CA",
"postal_code": "94102",
"country": "US"
},
"status": "ACTIVE",
"created_at": "2026-01-23T18:06:53.155Z",
"updated_at": "2026-01-23T18:06:53.155Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.