Typical flow
-
Check what the user can do
Call
GET /v2/transactions/context/{userAddress}/{network}/{vaultId}to fetch the user’s balances, limits, supported actions, required steps, and rewards context for that vault. -
Build the transaction payload
Call
GET /v2/transactions/{action}/{userAddress}/{network}/{vaultId}with the action you want to prepare. IncludeassetAddressand eitheramountfor a specific amount orall=truefor a full redeem-style action. - Send the returned transaction with the user’s wallet The response includes the target address, calldata, and value. You do not need to encode the vault contract call yourself.
| Capability | How to call | Required inputs |
|---|---|---|
| Check available vault actions | GET /v2/transactions/context/{userAddress}/{network}/{vaultId} | Path: userAddress, network, vaultId |
| Build deposit, redeem, request, or claim calldata | GET /v2/transactions/{action}/{userAddress}/{network}/{vaultId} | Path: action, userAddress, network, vaultId. Query: assetAddress, plus amount or all=true when the action requires an amount |
| Check claimable rewards | GET /v2/transactions/rewards/context/{userAddress} | Path: userAddress |
| Build rewards claim calldata | GET /v2/transactions/rewards/claim/{userAddress} | Path: userAddress. Query: claimIds |
| Add transaction attribution | GET /v2/transactions/suffix/{userAddress}/{vaultId} | Path: userAddress, vaultId |

