/messari/assets

POST /api/messari/assets

Price: 1 credit

Get a cryptocurrency's full Messari profile and market data by slug or ticker symbol

How to use it

Get the full Messari profile for a crypto asset by its slug (e.g. 'bitcoin') or ticker symbol (e.g. 'BTC'). Returns name, symbol, an editorial overview, sector and sub-sectors, tags, official links, plus market data: live price, 24h trading volume, circulating / fully diluted market cap, market cap dominance and rank, circulating / total / max supply, all-time high with date and percent down from it, cycle low, market count, number of exchanges traded, latest daily protocol fees and revenue in USD, first trade date, and price change percentages over 1h, 24h, 7d, 30d, 90d and 1y windows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• asset string required — Asset slug or ticker symbol (examples: "bitcoin", "ethereum", "BTC", "solana"; minLength: 1)

Response

• @type string (default: "MessariAsset")
• id string required
• name string nullable
• slug string nullable
• symbol string nullable
• about string nullable
• sectors array (default: [])
• sub_sectors array (default: [])
• tags array (default: [])
• links array (default: [])
  • @type string (default: "MessariAssetLink")
  • name string nullable
  • type string nullable
  • url string required
• price number nullable
• market_cap number nullable
• fully_diluted_market_cap number nullable
• market_cap_dominance number nullable
• volume_24h number nullable
• market_cap_rank integer nullable
• sector_rank integer nullable
• circulating_supply number nullable
• total_supply number nullable
• max_supply number nullable
• ath number nullable
• ath_date string nullable
• percent_down_from_ath number nullable
• cycle_low number nullable
• cycle_low_date string nullable
• market_count integer nullable
• exchange_count integer nullable
• fees_daily_usd number nullable
• revenue_daily_usd number nullable
• trade_start string nullable
• price_change_percentage_1h number nullable
• price_change_percentage_24h number nullable
• price_change_percentage_7d number nullable
• price_change_percentage_30d number nullable
• price_change_percentage_90d number nullable
• price_change_percentage_1y number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Asset not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.