Skip to main content
The Vaults.fyi borrowing API gives wallets and apps one integration for borrow market data, user-level lending and borrowing positions, market history, and ready-to-sign transaction payloads. Instead of building separate integrations for each lending protocol, you can use a normalized borrow market model across supported networks and protocols. This lets you show users what they have supplied, what they have borrowed, their risk metrics, and which actions are available before you build a transaction.
Borrowing is currently a Beta API surface. The endpoints are functional and tested, but may still change before general availability. Check the Beta API Reference section before integrating.

​
What you can build

Borrow market discovery

List supported borrow markets, filter by network, and inspect supplied assets, borrowed assets, rates, utilization, and collateral configuration.

User borrow positions

Show a wallet’s supplied and borrowed balances across supported markets, including position value and market-specific asset balances.

Risk metrics

Surface LTV, liquidation thresholds, health factor, and collateral data so users understand the state of their borrow positions.

Borrow transactions

Generate ready-to-sign supply, withdraw, borrow, and repay payloads after checking balances, limits, and available actions.

​
Integration flow

1

Discover markets

List supported borrow markets, optionally scoped to one network. Use market details to render assets, rates, utilization, and collateral parameters in your product.
2

Fetch the user's positions

Retrieve the wallet’s borrow portfolio to show supplied assets, borrowed assets, position value, and risk metrics across markets.
3

Check transaction context

Before rendering action buttons, fetch transaction context for the user, market, and asset. The response tells you which actions are available and which inputs are required.
4

Generate the transaction

Build a ready-to-sign payload for the selected action: supply, withdraw, borrow, or repay. Pass the payload to the user’s wallet for signing.

​
Borrow market data

Borrow markets expose the normalized data needed to build market screens and position pages:
  • Market identity: network, market ID, protocol, and supported assets
  • Rates and utilization
  • Supplied and borrowed asset data
  • Collateral and liquidation parameters
  • An optional borrowRateMultiplier where the protocol applies a collateral risk multiplier to the base borrow rate
  • Historical market data where available
Use this data for borrow dashboards, market comparison views, and account-specific borrow screens. Aave V4 Standard Spoke markets on Ethereum use this normalized model for discovery, positions, and transaction construction alongside the other supported lending protocols.

​
Positions and events

Borrow portfolio endpoints let you inspect a user’s current positions and market-level history:
  • Supplied assets and balances
  • Borrowed assets and balances
  • LTV, health factor, and other risk metrics where available
  • Asset-level position views for a specific market
  • User events for a market and asset
The wallet-wide borrow position list includes only markets with outstanding debt. Supply-only and collateral-only markets are omitted. Asset filters and the USD-value threshold can also exclude a market if no borrowed asset remains in the response. Use the single-market or asset-level position endpoint to inspect a known position without debt. When combining results across markets, deduplicate balances by assets[].positionId. The same economic position can appear in more than one market.

​
Transaction support

Borrow transaction endpoints follow the same pattern as vault transaction flows:
  1. Fetch context for the user, market, asset, and network.
  2. Confirm which action is available.
  3. Generate the action payload with amount or all=true where required.
  4. Pass the returned transaction to the user’s wallet.
Supported actions depend on the market and user state, but the model covers supply, withdraw, borrow, and repay flows. Read the action lists from transaction context: some protocols also require enableCollateral or enableController. Do not assume every supply flow consists only of approval and supply.
Always fetch transaction context before generating a borrow transaction. Borrow actions depend on collateral, balances, market limits, and protocol-specific constraints.

​
API reference

See the current endpoint guide in Beta.