v1.0
API reference Vaultody
PUT /vaults/{vaultId}/vault-accounts/{vaultAccountId}/add-asset

Add Asset to Address

This endpoint adds a specific asset to an existing vault account and creates an address for it if one does not already exist, enabling the asset to be tracked, receive balances, and be used in future transactions.

Path parameters

vaultAccountId string required
Unique identifier of the vault account to which the asset will be added.
vaultId string required
Unique identifier of the vault that owns the vault account.

Query parameters

context string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.

Body parameters application/json

context string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
data object required
item object required
address string e.g. 0xa5bd60af2ed1499ce8292bb2e6c0179dcea34f...
Address to associate with the asset. Used when the target address for adding the asset already exists in the vault account. Optional, but required if label is not provided.
assetId string required e.g. 6913471c6b2794841dc8fb84
Unique identifier of the asset to be added.
label string e.g. Address name
Optional, but required if address is not provided. Used when there is no existing address for the asset in the vault account.

Response

Returns 200 the request has been successful.

apiVersion string required
Specifies the version of the API that incorporates this endpoint.
E.G. 2026-03-20
requestId string required
Defines the ID of the request. The `requestId` is generated by Vaultody and it's unique for every request.
E.G. 601c1710034ed6d407996b30
context string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user.
E.G. yourExampleString
data object required
item object required
address string required
Blockchain address associated with the asset.
E.G. 0xa5bd60af2ed1499ce8292bb2e6c0179dcea34f33
assetUnit string required
Ticker symbol of the added asset (e.g.,ETH, BTC, TRX, USDT).
E.G. ETH
balance string required
Current balance of the asset in the address.
E.G. 0
contractAddress string required
Smart contract address of the token.
E.G. 0xdac17f958d2ee523a2206206994597c13d831ec7
decimals string required
Number of decimal places supported by the asset.
E.G. 6

Errors

400 The pagination attributes that have been used are invalid. Please check the Documentation to see details on pagination. application/json
401 The provided API key is invalid. Please, generate a new one from your Dashboard. application/json
403 Mainnets access is not available for your current subscription plan, please upgrade your plan to be able to use it. application/json
404 The specified resource has not been found. application/json
409 The data provided seems to be invalid. application/json
415 The selected Media Type is unavailable. The Content-Type header should be 'application/json'. application/json
422 Your request body for POST requests must have a structure of { data: { item: [...properties] } } application/json
429 The request limit has been reached. There can be maximum {requests} requests per {seconds} second(s) made. Please contact our team via email if you need more or upgrade your plan. application/json
500 An unexpected server error has occurred, we are working to fix this. Please try again later and in case it occurs again please report it to our team via email. application/json

No matches.