Skip to main content
Market state is readable through three channels: the REST API (best for dashboards and monitoring), the TypeScript SDK (best for integrations that compute derived values on-chain), and direct Solana RPC reads (for the lowest-level access). Most curators use the API for monitoring and the SDK for any integration that needs to react to market state.

Channels at a glance

List all markets

Returns the full set of klend markets the API knows about, with addresses and basic metadata.

Market-wide TVL and totals

Per-reserve metrics

Historical reserve metrics

Historical time-series data is API-only. The SDK reads live state; the API serves historical series.

Rewards data

The Kamino API exposes reward data such as active campaigns and per-user claimable amounts for klend reserves.

All active reward programs

A user’s claimable rewards across all reserves

Live farm state from the SDK

For real-time emission rates and on-chain farm balances, read the KFarms FarmState directly:
For the full APY calculation walkthrough, see Calculate reserve reward APY.

What the SDK exposes per reserve

reserve instances loaded via market.getReserves() provide the following getters:

Direct RPC reads

For the lowest-level access (minimal dependencies, fastest reads, no SDK abstraction), fetch the on-chain accounts directly via Solana RPC and decode them with the program’s IDL or struct definitions. The relevant accounts: See Programmatic integration for routing to the SDK and API documentation that covers each surface in depth.

Reference

Full API Reference

OpenAPI-rendered reference for every endpoint

SDK examples

Working code examples in the klend-sdk repo

Programmatic integration

Where to go for SDK / API / RPC integration docs

Farms & rewards

Curator-side farm management