View the full API reference for the get vault
details endpoint.
Usage
- REST API
Make a The following fields are provider-specific:
GET request to:Parameters
string
required
The unique identifier for the vault.
Returns
string
The vault’s unique identifier.
string
Display name of the vault.
"morpho" | "aave" | "veda"
The protocol powering the vault. Some response fields vary by provider (see below).
string
The onchain address of the vault contract.
object
The vault’s underlying asset.
string
Chain identifier in CAIP-2 format.
number | null
Current APY in basis points (e.g.
500 = 5%). See the note below on when this is null.number | null
The application’s share of the APY in basis points. See the note below on when this is
null.number | null
Total value locked in the vault in USD. See the note below on when this is
null.number | null
Liquidity available for withdrawal in USD. See the note below on when this is
null.string
The ID of the vault’s admin wallet, which receives your app’s share of fees.
string
The onchain address of the vault’s admin wallet.
number
Morpho vaults only. Additional token-incentive rewards APR, in basis points.
string
Aave vaults only. Performance fees currently available for your app to collect, in the smallest unit of the underlying asset. This is your app’s share after the revenue split. Collect it with the collect fees endpoint.
For Morpho and Aave vaults,
user_apy, app_apy, tvl_usd, and available_liquidity_usd
are always populated. For Veda vaults, available_liquidity_usd is always null, and
user_apy, app_apy, and tvl_usd may be null for the first 7–10 days after the vault is
deployed, after which they are populated.Example
Morpho vault
Aave vault
Next steps
Webhooks
Track deposit, withdrawal, and claim activity in real time.

