/solscan/tokens

POST /api/solscan/tokens

Price: 1 credit

Get a Solana token's profile and market data by its mint address

How to use it

Get the full profile of a Solana SPL token by its mint address. Returns name, symbol, icon, decimals, total supply, current USD price, market cap, holder count, the mint/freeze/update authorities, creator, creation and first-mint times, royalty (seller fee basis points), mutability, a token quality score, and social/extension links (website, twitter, telegram, discord, CoinGecko/CoinMarketCap ids).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• address string required — Token mint address (base58) (examples: "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v")

Response

• @type string (default: "SolscanToken")
• address string required
• name string nullable
• symbol string nullable
• image string nullable
• decimals integer nullable
• total_supply number nullable
• supply_raw string nullable
• price number nullable
• market_cap number nullable
• holder_count integer nullable
• token_authority string nullable
• freeze_authority string nullable
• update_authority string nullable
• creator string nullable
• created_at integer nullable
• first_mint_at integer nullable
• created_tx string nullable
• first_mint_tx string nullable
• seller_fee_basis_points integer nullable
• is_mutable boolean nullable
• token_score integer nullable
• extensions object nullable
  • @type string (default: "SolscanTokenExtensions")
  • website string nullable
  • twitter string nullable
  • telegram string nullable
  • discord string nullable
  • medium string nullable
  • description string nullable
  • coingecko_id string nullable
  • coinmarketcap_id string 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 — Token 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.