Protocols API

Available Endpoints

The Protocols API is organized into three main categories:

Core Protocols

List All Protocols - Returns a complete list of all available protocols supported by Messari, along with core metrics.
List Protocols Core Metrics - Returns a list of timeseries core metrics available for all protocols.
Get Protocol Core Timeseries - Returns timeseries data for a specific protocol’s core metrics.

DEX Protocols

List DEX Protocols - Returns all available DEX protocols supported by Messari.
List DEX Metrics - Returns a list of timeseries metrics available for DEXs.
Get DEX Timeseries - Returns timeseries data for a specific DEX protocol.

Lending Protocols

List Lending Protocols - Returns all available lending protocols supported by Messari.
List Lending Metrics - Returns a list of timeseries metrics available for lending protocols.
Get Lending Timeseries - Returns timeseries data for a specific lending protocol.
List Lending Instance Metrics - Returns a list of timeseries metrics available at instance grain.
Get Lending Instances Timeseries - Returns one timeseries per instance of a lending protocol.
List Lending Markets - Returns a filterable list of individual lending markets.
List Lending Market Metrics - Returns a list of timeseries metrics available at market grain.
Get Lending Markets Timeseries - Returns one timeseries per market of a lending protocol.

Interoperability Protocols

List Interoperability Protocols - Returns all available interoperability (bridging) protocols supported by Messari.
List Interoperability Metrics - Returns a list of timeseries metrics available for interoperability protocols.
Get Interoperability Timeseries - Returns timeseries data for a specific interoperability protocol.

Liquid Staking Protocols

List Liquid Staking Protocols - Returns all available liquid staking protocols supported by Messari.
List Liquid Staking Metrics - Returns a list of timeseries metrics available for liquid staking protocols.
Get Liquid Staking Timeseries - Returns timeseries data for a specific liquid staking protocol.

Lending and DEX metrics

Lending and DEX protocols carry the additional metrics below. Coverage varies by protocol: not every protocol reports every field, and one that does not returns null. Check for null rather than assuming a value is present.

Lending

Available on List Lending Protocols and on Get Lending Timeseries at 1d and 1w granularity.

Field	Definition
`depositsUsd`	Value deposited with the lending protocol, in USD.
`borrowedUsd`	Total value of assets borrowed from the protocol, in USD.
`interest24HourUsd`	Interest paid by borrowers, in USD.
`netInterestIncome24HourUsd`	Interest earned less the interest paid out to depositors, in USD.
`flashLoanFees24HourUsd`	Fees earned on flash loans, in USD.
`liquidationFees24HourUsd`	Fees earned on liquidations, in USD.
`royalties24HourUsd`	Royalties paid to the protocol, in USD.
`revenueUsd`	Daily lending revenue in USD: net interest income plus flash loan, liquidation and royalty fees. Timeseries only.

depositsUsd is a balance and carries no 24Hour qualifier, so it aggregates as an average over a longer granularity. The existing netDeposits24HourUsd is a daily flow, and the two are not interchangeable. Likewise flashLoanFees24HourUsd is a fee, while the existing flashLoanVolume24HourUsd on DEX protocols is a volume.

revenueUsd is the Blockworks Research lending revenue. It is not revenue24HourUsd, which comes from a different source and is served by the core protocol and network endpoints. The two measure different things and report different values for the same protocol on the same day. Keep them apart.

Lending grains

Lending data is served at three grains. Each one is a separate dataset with its own metrics and its own route:

Dataset	Grain	Example	Metrics
`lending`	Protocol	Aave	16
`lending-instances`	Product on a chain	aave-v3 on ethereum	10
`lending-markets`	Individual pool	an aave-v3 pool on ethereum	3

The two finer grains return many series in one response, so their shape differs from the protocol-grain endpoint. Each entry carries its own id and its own dimensions, and metadata.pointSchemas names the columns of every points row:

{
  "data": {
    "series": [
      {
        "id": "aave_aave-v3_arbitrum_0x794a61358d6845594f94dc1db02a252b5b4814ad",
        "marketName": "arbitrum-core",
        "productSlug": "aave-v3",
        "chain": "arbitrum",
        "points": [[1748736000, 1553455825.6, 794874331.0, 758581494.6]]
      }
    ]
  },
  "metadata": {
    "pointSchemas": [
      { "name": "Timestamp", "slug": "time", "is_timestamp": true },
      { "name": "Deposits (USD)", "slug": "depositsUsd", "is_timestamp": false },
      { "name": "Borrowed (USD)", "slug": "borrowedUsd", "is_timestamp": false },
      { "name": "TVL (USD)", "slug": "tvl24HourUsd", "is_timestamp": false }
    ],
    "granularity": "1d",
    "seriesCount": 23
  }
}

marketName is present on the lending-markets dataset only. Both finer grains serve 1d only. The protocol grain still serves 1d and 1w.

Blockworks Research maps a fraction of lending protocols. A protocol it does not map returns 200 with an empty series list, not a 404. A 404 means the identifier is not a Messari protocol at all. Note also that a product slug is not a protocol identifier: pass aave, not aave-v3.

Finding instances and markets

List Lending Protocols carries an instances array on each protocol, so you can see which products and chains a protocol reports before you request a timeseries:

"lending": {
  "depositsUsd": 29279393027.2,
  "instances": [
    { "productSlug": "aave-v2", "chain": "ethereum" },
    { "productSlug": "aave-v3", "chain": "ethereum" }
  ]
}

The array is empty for a protocol that Blockworks Research does not map. Instances need no listing of their own, because the per-protocol route returns all of them. Markets do: their ids are pool addresses, and there are thousands. Use List Lending Markets to discover them, filtered by protocol, product or chain. The protocol object on each row is the parent protocol, so its slug passes straight back as the protocol filter. The specific product is the sibling productSlug field, which the product filter matches:

{
  "marketId": "aave_aave-v3_arbitrum_0x794a61358d6845594f94dc1db02a252b5b4814ad",
  "marketName": "arbitrum-core",
  "productSlug": "aave-v3",
  "chain": "arbitrum",
  "protocol": { "id": "675b85dc-…", "name": "Aave", "slug": "aave" }
}

marketId is a composite of parent slug, product slug, chain and market key. It is keyed on the pool address rather than the market name, so it survives an upstream rename. Some source rows carry no name; marketName is then the market key, and it can be an empty string.

Response caps

A single request returns at most 100 instance series or 250 market series. Above that the request returns 400 and names the filters that narrow it. Pass product and chain to the markets timeseries route to stay under the cap — a large protocol such as Euler or Morpho needs them.

DEX

Available on List DEX Protocols and on Get DEX Timeseries at 1d and 1w granularity.

Field	Definition
`correlatedVolume24HourUsd`	Volume traded between correlated assets, in USD.
`aggregatorVolume24HourUsd`	Volume the exchange received through aggregators, in USD.
`platformVolume24HourUsd`	Volume traded directly on the exchange’s own front end, in USD.
`aggregatorTradeCount24Hour`	Number of trades the exchange received through aggregators.
`platformTradeCount24Hour`	Number of trades made directly on the exchange’s own front end.

DEX volume splits

Three more DEX fields are available on the listing endpoint only, not on the timeseries endpoints:

Field	Definition
`memecoinVolumeShare`	Share of 24 hour volume traded in memecoins, as a fraction between 0 and 1 — not a percentage.
`volumeByCategory`	24 hour volume split across asset categories, in USD.
`volumeByPair`	24 hour volume split across trading pairs, in USD.

volumeByCategory has the keys nativeStablecoin, chainToken, foreignToken, stablecoinSwaps, lstSwaps, composites, tokenizedAssets, projectTokens and memes. volumeByPair has the keys bitcoinUsd, ethereumUsd, solanaUsd, avalancheUsd, bnbUsd, bitcoinEthereum, bitcoinSolana, ethereumSolana, fx and eurUsd. Both objects are omitted entirely for a protocol that reports no split at all. Within an object that is present, a category or pair with no reported volume is null. An absent object and a null value therefore carry different meanings: the first means the protocol reports no split, the second means the protocol reports a split but not for that one category or pair.

Key Features

Multi-Chain Aggregation: Protocol data aggregates all deployments across multiple blockchain networks (e.g., Uniswap includes V3, V2, and V1)
Comprehensive Metrics: Access volume, TVL, fees, and other key protocol metrics
Flexible Time Ranges: Query data with various granularities from 1-minute to 1-year intervals
Historical Data: Access historical protocol performance data for analysis and tracking

Use Cases

The Protocols API enables developers to:

Build DeFi analytics dashboards tracking protocol performance
Compare metrics across different protocols and protocol types
Monitor DEX trading volumes and liquidity trends
Track lending protocol utilization and interest rates
Create alerts based on protocol metric thresholds
Analyze protocol growth and adoption over time

Getting Started

Assets & Market Data (included with Enterprise)

Exchanges (included with Enterprise)

Markets (included with Enterprise)

News

Topics API

Research

Research (Basic)

Stablecoins

Networks

Protocols

Token Unlocks

Fundraising

AI

Signals

Monitoring

Intel

Bulk API

Watchlists

Developer Resources

Available Endpoints

Core Protocols

DEX Protocols

Lending Protocols

Interoperability Protocols

Liquid Staking Protocols

Lending and DEX metrics

Lending

Lending grains

Finding instances and markets

Response caps

DEX

DEX volume splits

Key Features

Use Cases

​Available Endpoints

​Core Protocols

​DEX Protocols

​Lending Protocols

​Interoperability Protocols

​Liquid Staking Protocols

​Lending and DEX metrics

​Lending

​Lending grains

​Finding instances and markets

​Response caps

​DEX

​DEX volume splits

​Key Features

​Use Cases

Available Endpoints

Core Protocols

DEX Protocols

Lending Protocols

Interoperability Protocols

Liquid Staking Protocols

Lending and DEX metrics

Lending

Lending grains

Finding instances and markets

Response caps

DEX

DEX volume splits

Key Features

Use Cases