The Vaults.fyi transaction API lets you integrate vault interactions — deposits, redemptions, and reward claims — across hundreds of protocols without writing any protocol-specific contract logic. You get back ready-to-sign transaction payloads that users submit directly to the protocol. No intermediary smart contracts sit between your users and their funds.Documentation Index
Fetch the complete documentation index at: https://docs.vaults.fyi/llms.txt
Use this file to discover all available pages before exploring further.
Supported actions
The API supports the following vault interaction types:| Action | Description |
|---|---|
deposit | Move tokens into a vault to start earning yield |
redeem | Withdraw tokens from a vault in a single step (for instant-redeem vaults) |
request-redeem | Submit a withdrawal request for vaults with a queue or delay |
claim-redeem | Claim tokens after a withdrawal request has been fulfilled |
claim-rewards | Collect accrued reward tokens from a vault or across multiple vaults |
Not all vaults support every action. Use the transaction context endpoint to check which actions are available for a specific vault and user before rendering UI controls.
How transaction preparation works
Fetch transaction context
Call
GET /v2/transactions/context/ with the vault address, network, and user wallet address. The response tells you which actions are available, the user’s current position and balances, and any claimable rewards.Generate a transaction payload
Call
GET /v2/transactions/{action}/ with the action you want to prepare (e.g., deposit), the vault, the amount, and the user address. The API returns a fully formed transaction payload — including calldata, to-address, and value — ready to be signed.Present the transaction to the user
Pass the payload to your wallet integration (e.g.,
eth_sendTransaction for EOA wallets, or a UserOperation for ERC-4337 smart wallets). The user signs and submits directly to the protocol.EOA and smart wallet support
The API works with both externally owned accounts (EOA) and ERC-4337 compatible smart contract wallets.- EOA wallets
- Smart contract wallets
For standard wallets (e.g., MetaMask, Coinbase Wallet), the API returns a single transaction object. Pass it directly to your wallet library and prompt the user to sign.The user’s transaction goes straight to the protocol contract — no proxy or intermediary contract is involved.
Key properties
Non-custodial
Users transact directly with protocol smart contracts. Vaults.fyi never holds or controls user funds.
No extra contracts
The API prepares calldata for the protocol’s own contracts. No proxy or aggregator contracts are inserted.
Multi-vault rewards
The rewards endpoint discovers claimable rewards across all supported vaults for an address and generates batched claim payloads.
TVL tracking and rebates
Transactions generated by Vaults.fyi include attribution metadata so integrations can track TVL flows and support fee rebate programs where available.
TVL tracking and fee rebates
Transactions created with the Vaults.fyi Transactions API include attribution metadata automatically. This lets your integration track deposits, withdrawals, and current attributed TVL in portal.vaults.fyi. The same attribution layer can also support monetization through fee rebate programs where they are available. In those cases, the transaction metadata identifies the integration that originated the flow, making it possible to connect vault activity back to the partner that drove it. If you use the Transactions API, no extra work is required — the returned payload already includes the tracking suffix. If you build transactions yourself, use the free attribution suffix endpoint and append the returned suffix to your calldata. See TVL Tracking for Integrators for the full setup guide.API reference
See the full endpoint reference at /api/transactions, or explore the live spec athttps://api.vaults.fyi/v2/documentation/.