Crypto Data API - Messari and Blockworks Asset Metrics

Export crypto asset, market, onchain, fundraising, token unlock, news, research and intel data from the Blockworks API (which now also serves the Messari data) into an Apify dataset with your own Blockworks API key: 40k+ assets, any of 46 data tables and 61 timeseries models, and analyst-verified developments.

This actor wraps the Blockworks REST API at api.blockworks.com, the standardized interface behind the Messari and Blockworks research platforms. It turns a table name and filters, a list of slugs or symbols, or a timeseries model and series keys into clean, deduplicated rows you can download as JSON, CSV or Excel, schedule on a timer, or feed into trading models, research dashboards, spreadsheets, data warehouses and AI agents. Bring your own API key.

What it does

• Crypto screener over any data table: assets (name, symbol, sectors, stablecoin and wrapped flags, contracts, circulating market cap and rank), blockchains, markets, perpetual markets, funding rounds, investors, funds and fund managers, acquisitions, the news feed, research reports, stablecoins, tokenized equities and commodities, ETFs, digital asset treasury companies, spot and perp DEXs, lending protocols and markets, vaults, launchpads and token transparency filings. Filter with the table's documented operators, sort and page through everything.
• Lookup by slug, symbol or ID: one row per identifier, such as bitcoin, ETH or a UUID.
• Timeseries history: price candles (open, high, low, close, volume), market cap and dominance, supply, realized volatility, Sharpe ratio, protocol revenue, DEX and lending metrics, stablecoin supply by chain, issuer and currency, ETF flows, treasury holdings, token unlock schedules, sector market data and fundraising, social mindshare and sentiment, and trending topics, at 5 minute to monthly granularity.
• Slugs resolved for you: asset, blockchain and market keys given as a slug or symbol are resolved to the primary key first, because the timeseries routes return an empty series for a slug.
• Monitoring intel: analyst-verified developments and events across 1,000+ assets and 700+ sources, filtered by asset, category, importance, verification, governance and time, plus the intel taxonomy.
• Model catalogs: every table with its columns and filters, and every timeseries model with its granularities and access tier, or only the models your key can query.
• Pay only for results: a request the provider has nothing for becomes a free row that says why, never a charge.

Input

Field	Used by	What it does
mode	all	tabular (screener, default), tabularRow (lookup), timeseries, developments, events, categories, tabularCatalog or timeseriesCatalog
tabularModel	screener, lookup	The data table, such as assets, funding-rounds, news-feed or stablecoin-products
filters	screener	JSON object of documented field plus operator names: {"circulatingMarketcapRankLte": 100, "sectorIsOneOf": ["DeFi"]}. Undocumented names are dropped with a warning
sortBy, sortDirection	screener	A sortable field of the table and the direction
selections	screener, lookup, timeseries	Columns or metrics to return, such as close and volume
identifiers	lookup	Keys, slugs or symbols, one per line
timeseriesModel	timeseries	Such as asset-price, asset-marketcap, token-unlocks, protocol-revenue, sector-marketdata
granularity	timeseries	5m, 1h, 6h, 1d (default), 1w or 1n (month); each model supports a subset
seriesKeys	timeseries	Asset slugs, symbols or IDs, sector names, or IDs from the matching table; up to 20 per call, batched automatically
timeframe	timeseries	30d (default), ytd, 52w, 365d, 2025, 2025-06
startDate, endDate	timeseries, developments, events	YYYY-MM-DD, RFC3339 or unix seconds; replaces the timeframe
assetIds, intelCategories, intelSubcategories, minimumImportance, verifiedOnly, actionableOnly, governanceOnly, preTgeOnly, assetSectors, assetSubsectors, eventIds, search	developments, events	Monitoring filters
catalogScope	catalogs	All models, published models, or only those your key can query
maxResults	all	Row cap for the whole run (default 200)
requestsPerMinute	all	Pacing
apiKey	all	Your Blockworks API key, stored as a secret

How to get an API key

Create a key at app.blockworks.com/account/api (the same key covers the Data API, Monitoring and the MCP server; existing Messari API keys keep working). Most data tables need a paid Blockworks plan (Lite, Pro or Enterprise), and some datasets are sold separately; the catalog modes with the "Models my key can query" scope show exactly what your key reaches. Paste the key into the API key field or set the DATA_API_KEY environment secret. A run without a key ends cleanly with a message asking for one, before any request is sent.

Example output

{
  "mode": "timeseries",
  "modeLabel": "Timeseries points",
  "recordType": "timeseriesPoint",
  "model": "asset-price",
  "identifier": "bitcoin,ethereum",
  "found": true,
  "id": "1e31218a-e44e-4285-820c-8282ee222035|1788998400",
  "name": "Bitcoin",
  "slug": "bitcoin",
  "symbol": "BTC",
  "date": "2026-09-10T00:00:00.000Z",
  "value": 76547.51051673751,
  "retrievedAt": "2026-10-10T09:00:00.000Z",
  "note": null,
  "granularity": "1d",
  "seriesKey": "1e31218a-e44e-4285-820c-8282ee222035",
  "close": 76547.51051673751,
  "volume": 15639703479.254776,
  "units": { "close": "usd" }
}

Values are taken from the provider's documentation example. Timeseries points are unpacked from the API's compact arrays into named fields using its point schema, with the unix timestamp converted to an ISO date and the first metric copied to value. Table rows keep every field the provider returns, with the common columns (id, name, slug, symbol, date) filled from them.

FAQ

What is the Blockworks API, and how does it relate to the Messari API?

Blockworks is a crypto media and data company that acquired Messari in June 2026. The Blockworks API at api.blockworks.com is now the single REST interface to both companies' data: 15+ API families over 40k+ assets, documented publicly at docs.blockworks.com. The older Messari API is in maintenance. This actor calls only the current Blockworks routes, checked against the docs and the live host on 2026-10-10.

Do I need my own Blockworks API key?

Yes. This actor is bring your own API key and never ships one. The key is stored as an Apify secret, sent only in the documented X-Blockworks-API-Key header, and kept out of every log line. Without a key the run stops immediately with a clear message and no charge.

How do I get the top 100 crypto assets by market cap?

Use the screener on the assets table with the filter {"circulatingMarketcapRankLte": 100}, sort by circulatingMarketcapRank ascending, and run. Each row is one asset with its asset ID, slug, symbol, sectors, flags, contracts and market cap.

How do I download historical Bitcoin and Ethereum prices?

Pick the timeseries mode, the asset-price model and the 1d granularity, list bitcoin and ethereum as series keys, and set a timeframe such as 365d or a start and end date. Each row is one daily VWAP candle with open, high, low, close and volume in USD.

Can I get token unlock schedules?

Yes. The token-unlocks timeseries model gives the daily unlock schedule of an asset, past and future, keyed by the asset (slugs and symbols are resolved for you). Points run ahead of today to the end of the vesting schedule.

Which tables and models are there?

46 tables and 61 timeseries models, from assets, markets and perpetuals to fundraising, M&A, stablecoins, tokenized real-world assets, ETFs, treasury companies, DeFi protocols, news, research and token transparency. Run the catalog modes for the live list with every column, filter, granularity and access tier.

What are Monitoring developments?

Dated crypto events (a listing, a hack, a governance vote, an unlock) surfaced by agents across 700+ sources and verified by Blockworks intel analysts, each with a summary, categories, importance, source documents and resolved assets. Events group related developments over time.

What do I pay?

Pay per result: 0.005 USD per timeseries point, catalog model or category, 0.01 USD per data table row, and 0.02 USD per Monitoring development or event. Requests that find nothing are free. Your Blockworks subscription applies separately.

What happens if my key is wrong or my plan does not cover a table?

Blockworks checks the key before anything else and answers 403. The run then ends cleanly with a status message saying whether the key was rejected or the dataset is not on your plan, before anything is charged. A row, filter value or granularity the provider refuses becomes a free row with the provider's own explanation, and the run goes on.

Keyword map

crypto data API, Messari API, Blockworks API, crypto asset data, crypto market cap API, crypto price history API, Bitcoin historical price API, crypto screener API, token unlocks API, vesting schedule data, crypto fundraising data, crypto funding rounds API, stablecoin data API, tokenized assets data, crypto ETF data, protocol revenue API, DeFi data API, crypto mindshare and sentiment, crypto news API, crypto research reports, crypto intel alerts.

Terms and data use

Your Blockworks agreement decides what you may do with the data, and this actor does not change it. The Messari API terms that the Blockworks data API inherits describe it as intended for internal purposes and uses only, and ask anyone who wants to redistribute data from it to contact the provider's sales team first. Keep the run's dataset private, and do not republish it, unless your agreement allows sharing it.

Which routes were checked live: without a key the Data API routes normally, so every Data API route this actor builds was confirmed against an invented-route control (an invented path or model answers 404, a gated model 401, the catalogs 200), and the 46 tables and 61 timeseries models match the live catalogs. The Monitoring routes check authentication before routing, so they rest on the provider's published OpenAPI document. With any key sent, the gateway checks the key before routing. The legacy token-unlocks v1 routes are not used: they now answer with a crypto payment challenge, and the same schedules come from the token-unlocks timeseries model.