/coinmarketcap/coins/spotlight

POST /api/coinmarketcap/coins/spotlight

Price: 1 credit

Get spotlight cryptocurrencies for a category (trending, gainers, losers, recently added, most visited)

How to use it

Get a curated spotlight list of cryptocurrencies for the chosen category: 'trending', 'gainers' (biggest 24h winners), 'losers' (biggest 24h losers), 'recently_added' (newest listings), or 'most_visited'. Each coin includes name, symbol, rank, image, current price, market cap, 24h volume, and price change percentages over 1h/24h/7d/30d windows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Spotlight category to return (one of: "trending", "gainers", "losers", "recently_added", "most_visited")
• count integer required — Max number of coins to return (min: 1; max: 10)

Response

• @type string (default: "CoinmarketcapSpotlightCoin")
• id integer required
• name string required
• symbol string required
• alias string nullable
• rank integer nullable
• status string nullable
• image string nullable
• market_cap number nullable
• fully_diluted_market_cap number nullable
• price number 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
• volume_24h number nullable
• last_updated_at string nullable
• added_at 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 — The entity was not found, or a precondition failed 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.