POST /api/coinglass/spot/coins
Price: 1 credit
Get spot market data for a coin: price, market cap, volume and net flow
Get spot market data for one cryptocurrency: its supply and rank, and spot volume, buy/sell split, net flow and price change over windows from 5 minutes to 1 week.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string required — Coin ticker symbol (examples: "BTC"; minLength: 1)@type string (default: "CoinglassSpotCoin")symbol string requiredname string nullableimage string nullableprice number nullablemarket_cap number nullablerank integer nullablecirculating_supply number nullabletotal_supply number nullablemax_supply number nullableupdated_at integer nullablevolume_usd_5m number nullablebuy_volume_usd_5m number nullablesell_volume_usd_5m number nullablenet_flow_usd_5m number nullableprice_change_usd_5m number nullableprice_change_percentage_5m number nullablevolume_usd_15m number nullablebuy_volume_usd_15m number nullablesell_volume_usd_15m number nullablenet_flow_usd_15m number nullableprice_change_usd_15m number nullableprice_change_percentage_15m number nullablevolume_usd_30m number nullablebuy_volume_usd_30m number nullablesell_volume_usd_30m number nullablenet_flow_usd_30m number nullableprice_change_usd_30m number nullableprice_change_percentage_30m number nullablevolume_usd_1h number nullablebuy_volume_usd_1h number nullablesell_volume_usd_1h number nullablenet_flow_usd_1h number nullableprice_change_usd_1h number nullableprice_change_percentage_1h number nullablevolume_usd_4h number nullablebuy_volume_usd_4h number nullablesell_volume_usd_4h number nullablenet_flow_usd_4h number nullableprice_change_usd_4h number nullableprice_change_percentage_4h number nullablevolume_usd_12h number nullablebuy_volume_usd_12h number nullablesell_volume_usd_12h number nullablenet_flow_usd_12h number nullableprice_change_usd_12h number nullableprice_change_percentage_12h number nullablevolume_usd_24h number nullablebuy_volume_usd_24h number nullablesell_volume_usd_24h number nullablenet_flow_usd_24h number nullableprice_change_usd_24h number nullableprice_change_percentage_24h number nullablevolume_usd_1w number nullablebuy_volume_usd_1w number nullablesell_volume_usd_1w number nullablenet_flow_usd_1w number nullableprice_change_usd_1w number nullableprice_change_percentage_1w number nullablevolume_change_usd_1h number nullablevolume_change_percentage_1h number nullablevolume_change_usd_4h number nullablevolume_change_percentage_4h number nullablevolume_change_usd_12h number nullablevolume_change_percentage_12h number nullablevolume_change_usd_24h number nullablevolume_change_percentage_24h number nullablevolume_change_usd_1w number nullablevolume_change_percentage_1w number nullable422 — 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 — Coin 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.