Daily on-chain metrics for tokenized stocks with the Data API

What is the tokenized stocks datasetCopy Anchor Link

The BlockVectra Data API provides daily on-chain metrics and metadata for tokenized stocks. This dataset aggregates daily transfers, mints, burns, net supply changes, holder distributions, and decentralized exchange (DEX) trading metrics, enabling developers to track public activity for tokenized stocks.

For chains that offer this dataset, see the Supported Chains page.

• Base URL: https://dev-api.blockvectra.network/v1/data — except for GET /chains, all Data API routes are prefixed with a chain identifier (e.g. https://dev-api.blockvectra.network/v1/data/{chain}/…)
• Example chain: robinhood_mainnet (used as an example path parameter; check Supported Chains for all chains offering this dataset)
• Authentication: Provide your API key in the x-api-key: <your_api_key> request header
• Billing and coverage: Metered transparently in Compute Units (CU); only 2xx successful responses are billed. If a chain lacks stock coverage, the endpoint returns HTTP 422 no_coverage (not billed)

Daily leaderboard (GET /{chain}/stocks)Copy Anchor Link

The GET /{chain}/stocks endpoint returns a daily activity leaderboard of tokenized stocks for a specified UTC date, including display metadata (symbol, name, etc.), ordered by transfer activity descending (most active tokens first).

Request parametersCopy Anchor Link

• {chain} (path parameter, required): Chain identifier (for example, robinhood_mainnet).
• day (query parameter, optional): UTC calendar date in YYYY-MM-DD format. When omitted, defaults to the latest recorded day (if no activity is recorded, returns 200 with data: []). If provided but not a valid YYYY-MM-DD calendar date, returns HTTP 400 (error.code = "bad_request").
• limit (query parameter, optional): Caps the number of records returned. Defaults to 50; values above 500 are clamped to 500; passing 0 or a non-integer returns HTTP 400 (error.code = "bad_request").

Pagination behaviorCopy Anchor Link

This endpoint is not paginated. The limit parameter caps the maximum number of records returned. In the enclosing StockDailyListEnvelope (data and meta), stock endpoints do not return next_cursor (the key is absent entirely, never null).

Code examplesCopy Anchor Link

curl -s "https://dev-api.blockvectra.network/v1/data/robinhood_mainnet/stocks?day=2026-09-29&limit=10" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY"

Response structureCopy Anchor Link

The response envelope is StockDailyListEnvelope, containing data and meta:

• data (array): A list of daily leaderboard records (StockDaily), ordered by transfer activity descending (most active tokens first). Each item includes token identifiers (token, symbol, name), transfer activity (transfers, unique_senders, unique_receivers), supply metrics (mint_raw_amount, burn_raw_amount, net_supply_change), distribution metrics (holder_count, top10_holder_share_bps), DEX trading metrics (dex_swap_count, dex_raw_volume), and refresh timestamp (refreshed_at).
• meta (object): Chain metadata (chain, chain_slug, chain_external_id, as_of_block, finalized_block, coverage, refreshed_at). Stock endpoints do not return next_cursor.

Get one tokenized stock (GET /{chain}/stocks/{token})Copy Anchor Link

The GET /{chain}/stocks/{token} endpoint fetches metadata and up to 30 days of recent daily metrics for a specific tokenized stock by its token address.

Request parametersCopy Anchor Link

• {chain} (path parameter, required): Chain identifier (for example, robinhood_mainnet).
• {token} (path parameter, required): 20-byte token contract address; 0x prefix is optional and either case is accepted (returned addresses are normalized to 0x followed by 40 lowercase hex digits). An invalid address format returns HTTP 400 (error.code = "bad_request").
• If {token} is not a known tokenized stock, returns HTTP 404 (error.code = "not_found"). If {chain} is an unknown chain, returns HTTP 404 (error.code = "unknown_chain").

Code examplesCopy Anchor Link

curl -s "https://dev-api.blockvectra.network/v1/data/robinhood_mainnet/stocks/0x1111111111111111111111111111111111111111" \
  -H "x-api-key: $BLOCKVECTRA_API_KEY"

Response structureCopy Anchor Link

The response envelope is StockTokenEnvelope, containing data and meta:

• data (object): A StockToken object containing token contract metadata (address, symbol, name, decimals, created_block, created_tx_hash, factory, creator, mint_address, burn_address, refreshed_at) and recent daily metrics array daily.
  • daily (array): An array of recent daily metrics (StockDailyMetric), up to 30 days, ordered by date descending (newest first). Each daily item shares the same metrics schema as the leaderboard above (without the redundant token, symbol, and name fields).
• meta (object): Chain metadata object consistent with the leaderboard response; stock endpoints do not return next_cursor.

Key return fields explainedCopy Anchor Link

Daily metric fields (StockDaily and StockDailyMetric)Copy Anchor Link

Both the leaderboard and single-token historical daily items include the following core fields:

Token metadata fields (StockToken)Copy Anchor Link

When querying a single token, the outer data object contains contract metadata and recent daily metrics:

Encoding conventionsCopy Anchor Link

The API adheres to strict encoding rules across all endpoints to preserve numerical precision and consistency:

• Money-safety: Any value that can exceed 2^53 (256-bit integers such as mint_raw_amount, burn_raw_amount, net_supply_change, and dex_raw_volume) is serialized as a decimal string, never a JSON number and never scientific or hex notation. This prevents precision loss in runtimes like JavaScript. In JavaScript/TypeScript, parse with BigInt(str) (e.g. const net = BigInt(body.data.daily[0].net_supply_change)); in Python, parse with int(str). Counters staying well below 2^53 (transfers, unique_senders, unique_receivers, holder_count, top10_holder_share_bps, dex_swap_count, created_block) are plain JSON numbers.
• Binary and hex values: Addresses are 0x followed by 40 lowercase hexadecimal characters; hashes are 0x followed by 64 lowercase hexadecimal characters. All returned hex values are strictly lowercase.
• Timestamps and dates: Timestamps such as refreshed_at use YYYY-MM-DDTHH:MM:SSZ (ISO-8601 UTC with second precision). Daily aggregates (day) use plain calendar dates (YYYY-MM-DD).

Pagination notesCopy Anchor Link

Stock endpoints do not return next_cursor (these endpoints are not paginated; other Data API endpoints that support pagination pass next_cursor back via the cursor parameter). GET /{chain}/stocks uses the limit parameter to cap the maximum number of records returned (up to 500); GET /{chain}/stocks/{token} returns up to 30 days of recent daily metrics in the daily array, ordered by date descending (newest first).

Usage estimate (refreshing 50 tokens daily)Copy Anchor Link

Data API queries consume Compute Units (CU) based on platform method weights. The estimate below evaluates a scenario where 50 tokens each call GET /{chain}/stocks/{token} once daily, evaluated dynamically at build time against active method weights without hardcoded figures in prose:

Getting started and upgradingCopy Anchor Link

The free quota is ideal for development, testing, and lightweight workloads. When your traffic expands and requires higher concurrency or more compute units, make a paid top-up in the Console to upgrade to a paid account. After topping up, you are no longer constrained by the Free Plan's per-second call limit; each key remains subject to CU rate and burst limits, as described in the JSON-RPC documentation. Any unused Free Credits stay in your Credits and can still be used. For current rates and billing units, please see the Pricing page.