Integration with DeBank API for DeFi Portfolios
A user logs into your DeFi dashboard and sees empty screens: balances fail to load, protocol positions are not displayed. The reason is the lack of data aggregation across different blockchains. Manually collecting balances from Aave, Uniswap, Compound, and other contracts on Ethereum, Arbitrum, Polygon, and BNB Chain is a task that takes weeks if not months. The DeBank API solves this with a single call: ready-made aggregated data without your own indexing infrastructure. Our experience (5+ years in Web3, 30+ DeFi portfolio integrations) shows that this saves 80% of development time for a portfolio module and reduces infrastructure costs by 10x.
How to Get a User's DeFi Portfolio?
DeBank OpenAPI provides several groups of endpoints. The most common scenario is to get all tokens and protocol positions at once. For this, use /v1/user/all_token_list and /v1/user/complex_protocol_list. A direct RPC indexer requires weekly maintenance, while DeBank delivers results in minutes.
const headers = { AccessKey: process.env.DEBANK_API_KEY }
// All tokens for user on all chains
const tokens = await axios.get(
`https://pro-openapi.debank.com/v1/user/all_token_list?id=${userAddress}&is_all=true`,
{ headers }
)
// Positions in a specific protocol
const aavePositions = await axios.get(
`https://pro-openapi.debank.com/v1/user/protocol?id=${userAddress}&protocol_id=aave3`,
{ headers }
)
Data Model: What the API Returns
Each token in the response contains: chain (chain identifier), id (contract address), amount (quantity), price (current USD price), usd_value (total amount). For LP positions and protocol positions, the structure is more complex — nested objects with detail_types that describe the position type (lending, staking, vesting, etc.).
An important nuance: DeBank returns price: 0 for tokens without liquidity or with a price below the threshold. Do not interpret this as an error — it is normal for tail tokens. In such cases, we display "no price data" in the UI rather than zero.
Why DeBank Is Better Than a Custom Aggregator?
A custom indexer requires weekly maintenance, configuring RPC nodes, handling reorganizations and forks. DeBank API: 10x faster time to market and 90% cheaper to operate. Additionally, DeBank already accounts for custom tokens and complex protocols — your team doesn't spend time on reverse engineering.
How to Handle Rate Limits and Errors?
Why Is It Important to Cache DeBank Data?
DeBank Pro API rate limit is up to 300 requests per minute. For applications with hundreds of users, server-side caching is mandatory. Balance data changes rarely relative to RPC request time. A cache with TTL of 60–300 seconds suits most use cases.
Pattern: on a user data request — serve cached data immediately, trigger a background update. The user sees updated data on the next request.
async function getUserPortfolio(address: string) {
const cacheKey = `portfolio:${address}`
const cached = await redis.get(cacheKey)
if (cached) {
// Trigger background update
updateInBackground(address, cacheKey)
return JSON.parse(cached)
}
const fresh = await fetchFromDeBank(address)
await redis.setex(cacheKey, 120, JSON.stringify(fresh))
return fresh
}
| Caching Strategy |
TTL |
Applicability |
Infrastructure Cost |
| No cache |
0 |
Single queries |
High (rate limit) |
| Simple TTL |
60–300 s |
Most applications |
Medium |
| Background update |
60–300 s |
High load |
Low |
What to Do on Error 503?
DeBank API is an external service and may be unavailable. The application must properly handle 503, 429 (rate limit), and timeouts. On timeout — return cached data with a note about the last update time, rather than showing an empty screen. For critical functions (e.g., calculating collateral ratio for a lending product) — do not rely solely on DeBank. A fallback channel: direct RPC calls to contracts via wagmi/viem for the most important positions.
Typical Integration Mistakes
-
Ignoring ratio for LP tokens: DeBank returns the amount of LP tokens, but for valuation you need to substitute prices from the pool. Use the
/v1/user/pool endpoint or external AMM prices.
-
Mixing chains: responses for
chain_id=1 (Ethereum) and chain_id=137 (Polygon) may contain tokens with the same address — check the chain field.
-
Unhandled
price: 0: if not filtered, zero amounts appear in the UI, misleading users.
What Is Included in Turnkey Integration
- DeBank Pro API key setup and endpoint access
- Server-side caching with Redis implementation
- Error handling and RPC fallback
- UI components: tokens, protocols, history, NFTs
- Documentation and post-deployment support
Timeline and Cost
Basic integration (tokens + protocol positions + history) — 1-2 days. Full cycle (caching, error handling, UI) — up to 5 days. The exact cost is determined individually after project evaluation. Contact us to discuss details — our expertise in this area guarantees a reliable and scalable solution. Request integration and we will help you avoid typical mistakes.
DeFi Protocol Development
We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.
We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.
Why are oracles a critical component of DeFi?
Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.
Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.
TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.
Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.
| Oracle |
Mechanism |
Manipulation Protection |
Latency |
| Chainlink |
Median from independent providers |
High (decentralization) |
Up to 24h at 0% movement |
| Uniswap v3 TWAP |
Average price over N blocks |
High (hard to maintain) |
30 min – 1 h |
| Pyth Network |
Cross-chain low-latency |
Medium (dependent on publisher) |
Seconds |
In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.
How to protect a DeFi protocol from flash loan attacks?
Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.
Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.
Key Components of DeFi Architecture
| Protocol Type |
Core Mechanism |
Main Risk |
| DEX (AMM) |
x*y=k or concentrated liquidity |
impermanent loss, oracle manipulation |
| Lending |
collateral ratio, liquidation |
bad debt during cascading liquidations |
| Yield aggregator |
auto-compounding strategies |
rug via strategy upgrade |
| Derivatives / Perps |
funding rate, mark price |
liquidation cascades, socialized losses |
| Liquid staking |
stETH-style rebasing |
depegging on mass unstake |
AMM: From x*y=k to Concentrated Liquidity
Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.
Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.
Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.
Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.
Lending Protocols: Collateral, Liquidation, Bad Debt
LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.
Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.
If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.
Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.
Yield Farming and Incentive Mechanics
Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.
Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.
What Our DeFi Protocol Development Includes
- Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
- Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
- Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
- Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
- Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
- Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
- Post-launch support: updates, patches, upgrades via proxy.
Our Expertise and Experience
We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.
DeFi basic principles that we apply in practice.
Timelines
- DEX with AMM (Uniswap v2 fork): 6–10 weeks
- Lending protocol (Aave-style, single collateral): 3–5 months
- Yield aggregator with multiple strategies: 2–4 months
- Full-fledged DeFi protocol with governance: 5–8 months including audit
Cost is calculated individually—contact us for a project estimate.
Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.
