Historical Market Data

Fetch historical daily metrics for any ERC-20 token, including USD price, trading volume, and market capitalisation. Ideal for backtesting, trend analysis, and building time-series visualisations in dashboards or trading agents.

Endpoint

GET https://api.dapplooker.com/v1/crypto-market-historical

💡 Pro Tips

• This endpoint supports up to 1,000 items per page—ideal for bulk analytics or plotting historical charts efficiently. Use the query param page and pagination attributes to navigate through results.

• To fetch data for a token, pass any of these query parameters: token_address, token_id, or token_ticker.

• Use start_date and end_date to narrow down results to a custom date range, helping reduce payload size and focus on relevant timeframes.

• Combine this endpoint with others like Token Details, Trending Tokens, or Technical Indicators to create rich analytics, dashboards, or market sentiment tools.

• This endpoint is x402 payment–enabled, opening access for all users — simply pay and use without needing an API key.

Authentication

This endpoint supports two authentication methods:

Method	Description
API Key	Provide your Loky API key using the api_key parameter for authenticated access.
x402 Payment Protocol	If api_key is not provided, the request automatically uses the x402 protocol for on-chain payment verification.

For seamless integration, user can follow the x402 Quickstart Guide for Buyers.

Query Parameters

Parameter name	Type	Mandatory	Description
api_key	string	No	Your unique Loky API key used for authentication
chain	string	Yes	The network chain to query. Supported chains: base, solana
token_id	string	No	Unique token Id to fetch data
token_ticker	string	No	Token ticker (symbol) to fetch data
token_address	string	No	Token contract address to fetch data
page	integer	No, Default page 1	Page number, 1000 items per page
start_date	string	No	Date from where the data is need to fetch. Use format: YYYY-MM-DD
end_date	string	No	Date to where the data is need to fetch. Use format: YYYY-MM-DD

Sample Request

# Pagination enabled (via page parameter)
curl --location 'https://api.dapplooker.com/v1/crypto-market-historical?api_key=<API_KEY>&chain=base&token_address=0xac1bd2486aaf3b5c0fc3fd868558b082a531b2b4&page=1'

# With custom date range (start_date & end_date)
curl --location 'https://api.dapplooker.com/v1/crypto-market-historical?&api_key=<API_KEY>&chain=base&token_ticker=VIRTUAL&start_date=2025-01-01&end_date=2025-06-06'

Sample Response

{
  "success": true,
  "data": {
    "token_id": "toshi",
    "token_symbol": "toshi",
    "token_address": "0xac1bd2486aaf3b5c0fc3fd868558b082a531b2b4",
    "token_day_metrics": [
      {
        "date_time": "2025-06-03",
        "usd_price": 0.00058,
        "total_volume": 21583357,
        "market_cap": 243545744
      },
      {
        "date_time": "2025-06-02",
        "usd_price": 0.00054,
        "total_volume": 13218936,
        "market_cap": 228146173
      },
      {
        "date_time": "2025-06-01",
        "usd_price": 0.00056,
        "total_volume": 14565988,
        "market_cap": 238189967
      }
      // Upto 1000 items
    ],
    "meta": {
      "pagination": {
        "page": 1,
        "pageSize": 1000,
        "totalPages": 1,
        "totalRecords": 3
      }
    }
  }
}

Response Fields Explanation

• token_id (string): A unique assigned identifier for the token.

• token_symbol (string): The token’s ticker symbol, typically used in trading.

• token_address (string): The on-chain address (contract address) of the token.

• token_day_metrics (array): A list of daily market stats for the token. Each object includes:

  • date_time (string): The calendar date of the record in YYYY-MM-DD format.

  • usd_price (number): The token’s closing price in USD on that day.

  • total_volume (number): The total trading volume in USD on that day.

  • market_cap (number): The estimated market capitalization on that day (price × circulating supply), in USD.

Pagination Attributes:

• page (integer): The current given page number, also being returned in the response.

• pageSize (integer): The number of max items can be included per page.

• pageCount (integer): The total number of pages available.

• total (integer): The total number of items available across all pages.