Get Balance
Retrieves a user’s current liquidity balance and position within yield-generating vaults or pools across supported protocols and blockchain networks. This endpoint returns a numeric value representing the total liquidity available for the given address, with detailed breakdowns of both vault and pool balances. Users can query their balance either by providing a direct vaultAddress or by supplying a tokenAddress along with a vaultNumber, in addition to required parameters such as the user’s public address and yieldAggregatorId. This comprehensive data is essential for developers and users seeking to monitor yield positions, manage liquidity, track earned yields, and integrate real-time yield data into DeFi portfolio management and performance analytics tools.
💡 Compute Unit Value: 25 (Fixed)
Request
- Base URLhttps://svc.blockdaemon.com
- URLhttps://svc.blockdaemon.com/defi/v1/yieldaggregator/getbalance
- AuthAPI key in header X-API-Key
Query parameters
The public blockchain address of the user whose liquidity balance is being queried. This value specifies the owner of the tokens deposited in the yield aggregator.
The contract address of the token. Use this parameter when querying by token, in combination with vaultNumber, if the vaultAddress is not provided.
The identifier for the specific vault holding the token, used when multiple vaults exist for the same token. Provide this along with tokenAddress if not directly specifying vaultAddress.
The unique ID to specify the yield aggregator for queries or transactions.
The address of the yield vault. Use this parameter to directly query a specific vault instead of using tokenAddress and vaultNumber.
The unique blockchain address that identifies the specific yield market or vault within the yield aggregator. This parameter directs the query to the appropriate liquidity pool where deposits are made.
Pool's address.
Response
Successful response
Example response
{
"status": 200,
"msg": "success",
"data": {
"vaultBalance": "0",
"poolBalance": "0"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.