Assign a new Customer ID or update an existing one for one or more Ethereum validators.
This endpoint allows adding a Customer ID (customer_id) to validators that do not have one or updating the Customer ID for validators that are already assigned to a different customer.
Input example: updateEthDepositCustomerId(
customer_id="customer-123",
public_keys=[
"0xab28...6776a",
"0x91cd...4ba0"
]
)
Return: JSON containing confirmation of the update operation.
-------------------- Response --------------------
{
"FunctionData": {
"Status": "Success"
},
"Meta": {
"AccessToken": "a36fe...ff64de",
"Destination": "0455c55...7c467666",
"Source": "289d5...985",
"Time": "2025-02-05 10:06:40.811"
}
}
-------------------- Error Reference --------------------
| Error Type | Error Code | Reason / Description |
|---|
| Backend Response | 1007 | Invalid validator public key. |
| Backend Response | 1000 | No validators matching the provided filters were found in the system. |
| Backend Response | 1000 | Galaxy request failed. The response includes the error returned by Galaxy. |
Examples:
// Backend Response — Galaxy error (proxied)
{ "ErrorCode": "1007", "Reason": "validator public key 0x105...ae5 is invalid. reason - Validator public key must contain 96 digits, but it contains 95"}
// Backend Response — Galaxy error (proxied)
{ "ErrorCode": "1000", "Reason": "o validators matching the provided filters were found in the system."}
// Backend Response — Galaxy error (proxied)
{ "ErrorCode": "1000", "Reason": "Galaxy request failed. Reason: {\"error\": [{\"code\": 123, \"message\": \"Some error message\"}]}"}
customer_idstringThe ID of the customer to assign or update for the specified validators.
public_keysarray<p>A list of validator public keys to which the customer_id should be assigned or updated. A maximum of 50 entries are allowed.</p>