Get Coin Markets logo

Catalog action Blockchain Data

Get market data for cryptocurrencies with prices, market cap, volume, and supply metrics. Returns current price, 24h high/low/volume, price change percentages (24h, 7d, 14d, 30d, 1y), ATH/ATL, circulating/total/max supply, and optional 7-day sparkline. Sorted by market cap by default. Supports pagination (100/page, max 250), filtering by category (DeFi, Layer 1, Meme), and filtering by coin IDs. Ideal for: market overview dashboards, leaderboards, coin comparisons, category analysis, screeners.

At a Glance

FieldValue
Action IDcoingecko-get-coin-markets
CategoryBlockchain Data
ConnectorNot required
Requires gasNo
Funds movementNone declared
Tagscoingecko, market, price, cryptocurrency, market-cap, volume, rankings, read

Payload Schema

FieldTypeRequiredDescription
vsCurrencystringYesTarget currency for prices and market data (e.g., 'usd', 'eur', 'btc'). All prices will be in this currency.
idsarrayNoFilter by specific coin IDs. If provided, only returns data for these coins. Max 250 IDs.
categorystringNoFilter by category (e.g., 'decentralized-finance-defi', 'layer-1', 'meme-token'). Use get-categories action for full list.
orderstringNoSort order for results. Default: 'market_cap_desc'
perPagenumberNoNumber of results per page. Range: 1-250. Default: 100
pagenumberNoPage number for pagination. Default: 1
sparklinebooleanNoInclude 7-day sparkline price data. Default: false
priceChangePercentagestringNoInclude price change percentage for specific periods. Comma-separated: '1h,24h,7d,14d,30d,200d,1y'. Default: none

Result Schema

FieldTypeRequiredDescription
coinsarrayYesArray of coin market data
pagenumberYesCurrent page number
perPagenumberYesResults per page
totalCountnumberNoTotal number of results (if available)

Examples

json
{ "type": "coingecko-get-coin-markets", "payload": { "vsCurrency": "usd" }, "children": []}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.

Ask a question... ⌘I