Create Counterparty External Wallet
POST/v1/crossborder/counterparties/:id/wallets
Create a new external wallet for a crossborder counterparty. The wallet will be associated with the specified counterparty and will be created with PENDING status. Requires wallet address, network, currency symbol, and provider information.
Request
Path Parameters
Counterparty 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 transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
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
Wallet name.
Wallet address.
Network.
Currency symbol.
Provider.
Responses
- 201
- 400
- 401
- 422
Counterparty wallet created successfully.
- application/json
- Schema
- Example (from schema)
Schema
Wallet ID.
User ID.
Counterparty ID.
Wallet name.
Wallet address.
Network.
Currency symbol.
Provider.
Possible values: [ACTIVE, INACTIVE, PENDING, BLOCKED]
Wallet status.
Wallet created date.
Wallet updated date.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"user_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"counterparty_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"name": "My Bitcoin Wallet",
"address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
"network": "ethereum",
"currency_symbol": "USD",
"provider": "MetaMask",
"status": "PENDING",
"created_at": "2026-02-13T19:26:56.572Z",
"updated_at": "2026-02-13T19:26:56.572Z"
}
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.