Get vault data across providers

GET 
/v1/data/vaults

Returns public vault data across the supported ERC-4626-style providers on a single chain in one round-trip. The response is keyed by provider — only providers that resolved successfully are included; failed providers are omitted (no per-provider error envelope).

Supported providers

key	source
fluid	Fluid fTokens (ERC-4626 yield tokens) and vaults (NFT-position margin markets)
gearbox	Gearbox V3 passive PoolV3 (ERC-4626 Diesel shares)
morpho	Morpho Blue MetaMorpho vaults
silo	Silo V2 + V3 isolated lending vaults (GraphQL-backed)
euler-earn	Euler V2 Earn vaults (ERC-4626)

Response shape

The top-level object is keyed by provider name. Each provider's value is a free-form payload from @1delta/margin-fetcher's getVaultPublicDataAll — schemas diverge per provider (see the package's types for exact field shapes). Common fields across most providers: vault/share token address, underlying asset, supply rate, total assets / supply, and provider-specific metadata (e.g. Fluid vaultId, Silo siloAddress).

Related action endpoints

• GET /v1/actions/vaults/deposit — ERC-4626 deposit via the 1delta Composer, with optional Fluid native-deposit path.
• GET /v1/actions/vaults/withdraw — ERC-4626 withdraw via the 1delta Composer, with native-unwrap support.

For Fluid margin vaults (the NFT-position kind, not fTokens), the lending action endpoints (/v1/actions/lending/{deposit,withdraw,borrow,repay}) are the right surface — they understand the per-vault FLUID_<chainId>_<vaultId> lender keys and Fluid's NFT ownership model (including the pre-flight ownerOf validation for deposit-to-existing-NFT with a custom receiver).

Request

Responses

200

Provider-keyed vault data. Failed providers are omitted from the response (the worker logs a warning but does not propagate per-provider errors).

400

Validation error