Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Data querying

Euler data integrations usually combine indexed data, metadata, and direct contract reads. Choose the source based on whether you need display data, historical data, or onchain state for execution.

Choose a data source

  • Euler Data API V3: indexed and enriched data for applications and analytics, including chains, vaults, accounts, prices, APYs, rewards, liquidations, governance actions, and event timelines.
  • Lens contracts: current onchain vault, account, oracle, IRM, and Earn state aggregated for offchain reads.
  • Known vault endpoints: public HTTP endpoints for checking which vaults are known (initial configuration reviewed at listing time) and fetching their metadata (name, curator, deprecation status).
  • Using lens contracts: practical account, vault, health, LTV, and APY queries.
  • Subgraphs: lightweight GraphQL indexes hosted on Goldsky for discovering active deposit and borrow positions across all sub-accounts.
  • Direct calls, logs, and custom indexers: query vaults, EVC, and periphery contracts directly or maintain an index when the hosted interfaces do not cover your use case.

Euler state is distributed across vaults, EVC, and periphery contracts. Indexed data can lag chain state. For transaction validity, solvency, liquidation, or other execution-sensitive decisions, read or simulate against current onchain state on the target chain.