Update counterparty
Updates an existing counterparty's information including profile details, addresses, business relationships, and associated accounts.
This endpoint supports partial updates - only include the fields you want to modify.
Endpoint
PATCH/v2/counterparty/{counterpartyId}
Link
Request
Path Parameters
Parameter
Type
Description
Required
Example
counterpartyId
string
Counterparty ID to update.
Yes
"cp_12345"
Headers
Key
Value
Required
Authorization
123
Yes
Content-Type
application/json
Yes
Accept
application/json
Yes
Request Body
All fields are optional - only include fields that need to be updated.
json
Request Fields
1. Main Counterparty Fields
Field
Type
Required
Description
Example
description
string
No
Updated counterparty description.
"Updated supplier description"
2. Profile Object
Field
Type
Required
Description
Example
name
string
No
Updated legal name.
"Updated Corp Name"
phoneNumber
string
No
Updated contact phone.
"+19876543211"
taxNumber
string
No
Updated tax ID number.
"TAX-UPDATED-123"
dateOfBirth
string
No
Updated date of birth/incorporation.
"1985-05-15T00:00:00Z"
website
string
No
Updated company website.
"https://updated.com"
lastname
string
No
Updated last name (individuals).
"Updated Lastname"
3. Address Object
Field
Type
Required
Description
Example
addressLine1
string
No
Updated primary address.
"456 Updated Street"
addressLine2
string
No
Updated suite/floor.
"Suite 600"
addressLine3
string
No
Updated additional info.
"Building C"
city
string
No
Updated city.
"New York"
stateIso
string
No
Updated state code.
"NY"
countryIso
string
No
Updated country code.
"US"
postalCode
string
No
Updated postal code.
"10002"
unitNumber
string
No
Updated unit number.
"6B"
4. AdditionalInfo Object
Field
Type
Description
Allowed Values
Example
type
string
Updated legal structure.
INDIVIDUAL, CORPORATION
"CORPORATION"
businessLine
string
Updated industry type.
PLB_AUTOMOTIVE, PLB_RETAIL, etc.
"PLB_HIGH_TECH_SOFTWARE_TELECOMS"
relationship
string
Updated business relationship.
PRC_SUPPLIER, PRC_CUSTOMER, etc.
"PRC_SUPPLIER"
5. Accounts Array
Update existing accounts or add new ones. Required fields for account updates: accountId, currencyCode
Field
Type
Required
Description
Example
accountId
string
Yes
Existing account ID to update.
"acc_12345"
currencyCode
string
Yes
Currency code (ISO 4217).
"USD"
Bank Account Updates
Field
Type
Required
Description
Example
bank.name
string
No
Updated bank name.
"Updated Bank"
bank.number
string
No
Updated account number.
"987654321"
bank.routingNumber
string
No
Updated routing number.
"021000022"
Crypto Account Updates
Field
Type
Required
Description
Example
crypto.address
string
No
Updated crypto wallet address.
"0xupdatedAddress..."
crypto.additionalInformation.walletType
string
No
Updated wallet type.
"CPW_INSTITUTION"
Fiat Account Updates
Field
Type
Required
Description
Example
fiat.number
string
No
Updated account number.
"987654321"
fiat.swift
string
No
Updated SWIFT code.
"UPDATEDBIC"
fiat.routingNumber
string
No
Updated routing number.
"021000022"
fiat.additionalInformation.accountType
string
No
Updated account type.
"SAVING"
Response (200 OK)
Returns the updated counterparty object with all current information.
Example Response:
json
Response Fields
Field
Type
Description
Example
item.counterpartyId
string
Counterparty ID (unchanged).
"cp_12345"
item.customerId
string
Customer ID (unchanged).
"cust_12345"
item.customerName
string
Customer name (auto-populated).
"John Doe"
item.updatedAt
string
New update timestamp.
"2024-05-21T14:20:00Z"
item.accounts[].status
string
Account status (may change after updates).
"ACCEPT", "MODERATION"
Examples
Request
bash
Minimal Update Example
Request (update only phone number):
json
Response:
json
Account Update Example
Request (update bank account details):
json
Add Crypto Account Example
Request (add new crypto account):
json
Error Responses
Counterparty Not Found:
json
Account Not Found:
json
Validation Error:
json
Unauthorized:
json
Notes
Partial Updates: Only include fields that need to be changed
Account Updates: Use existing
accountIdto update accounts; new accounts without ID will be createdStatus Impact: Account updates may trigger re-verification (status change to
MODERATION)Audit Trail:
updatedAttimestamp reflects when changes were appliedField Validation: All updated fields undergo the same validation as creation
Update Scenarios:
Contact information changes
Address updates
Business relationship modifications
Account detail corrections
Adding new payment methods/accounts
Last updated

