Documentation / New API reference / Price
Get Price
Reference
Last reviewed 2026-10-07
Current price snapshot for an asset.
Try it
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
asset | query | string | Yes | Asset symbol, e.g. TAO. Matched case-insensitively. |
Responses
200 — Latest price observation for the asset
| Field | Type | Required | Description |
|---|---|---|---|
data | array | Yes | The snapshot, as a one-element array: data is always an array (docs/api_standards.md). |
data[].circulating_supply | string | Yes | Circulating supply (decimal string). |
data[].created_at | string | Yes | When this point entered the series (ISO 8601). |
data[].fully_diluted_market_cap | string | Yes | Fully diluted market capitalisation in USD (decimal string). |
data[].last_updated | string | Yes | CoinMarketCap's own last-touched time for the asset (ISO 8601). This is an entry-level stamp, not the quote's; read created_at for when we recorded the row. |
data[].market_cap | string | Yes | Market capitalisation in USD (decimal string). |
data[].market_cap_dominance | string | Yes | Share of total crypto market capitalisation, percent (decimal string). |
data[].max_supply | string | Yes | Maximum supply (decimal string). |
data[].name | string | Yes | Asset name, e.g. Bittensor. |
data[].percent_change_1h | string | Yes | 1-hour price change, percent (decimal string). |
data[].percent_change_24h | string | Yes | 24-hour price change, percent (decimal string). |
data[].percent_change_30d | string | Yes | 30-day price change, percent (decimal string). |
data[].percent_change_60d | string | Yes | 60-day price change, percent (decimal string). |
data[].percent_change_7d | string | Yes | 7-day price change, percent (decimal string). |
data[].percent_change_90d | string | Yes | 90-day price change, percent (decimal string). |
data[].price | string | Yes | Price in USD (decimal string). |
data[].slug | string | Yes | Asset slug, e.g. bittensor. |
data[].symbol | string | Yes | Asset symbol, e.g. TAO. |
data[].total_supply | string | Yes | Total supply (decimal string). |
data[].updated_at | string | Yes | Row write time (ISO 8601). Equal to created_at for every row. |
data[].volume_24h | string | Yes | 24-hour trading volume in USD (decimal string). |
pagination | object | Yes | Pagination block. One item on one page, or zero items for an asset the series does not carry. |
pagination.current_page | integer (int32) | Yes | 1-indexed page that produced the rows in data. |
pagination.next_page | integer (int32), nullable | Yes | Next page number, or null if this is the last page. |
pagination.per_page | integer (int32) | Yes | Number of items requested per page. |
pagination.prev_page | integer (int32), nullable | Yes | Previous page number, or null if this is the first page. |
pagination.total_items | integer (int64) | Yes | Number of items matching the query across all pages. This is the exact count — every matching row, however many there are. It is not bounded by total_pages, so a listing can legitimately report far more items than total_pages × per_page. |
pagination.total_pages | integer (int32) | Yes | Number of pages at the current per_page that this API will serve: ceil(total_items / per_page), capped at ceil(1000000 / per_page) because the page parameter only reaches into the first 1,000,000 rows. When the cap bites, total_items is still the true total and this is the last page a request can ask for; reach deeper history with the endpoint's range filters instead of a larger page. |
400 — Invalid query parameter
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
500 — Internal server error
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
Every request needs an Authorization header holding your API key — see Getting started with the Taostats API.