Endpoints · v1 / Chains
Every blockchain we track, with the same market aggregate /categories carries, plus three
fields a category does not have: a short display name, the EVM chain id, and a logo.
Everything /categories says about market never being null, about which groups appear,
about market_cap_share, and about top_gainers applies here unchanged — read those
sections first; only the differences are repeated below.
Not every chain in the world appears here, and not every chain we know about. A chain
gets a market aggregate only once it has active coins on it, so a catalogued chain with no
listed tokens produces no snapshot and is not in this response. Around half of the chains in
our directory are in that state. This is a real difference from /exchanges, where an
exchange with no aggregate is still listed with "market": null.
Query parameters
Identical to /categories: id, slug, page, size, limit, offset, sort. Same
caps, same default market_cap:desc, same sort keys — id, name, slug, market_cap,
volume_24h — sort=volume and sort=display_name are both a 400. slug is unique
upstream here too, so a single slug is a single-row lookup — and it needs the same
URL-encoding care: bnb-smart-chain-(bep20) is a live chain slug, and the & case
documented under /categories applies here too.
Response
Item fields
Everything under market is exactly as documented for /categories. The chain-level fields:
| Field | Type | Notes |
|---|---|---|
id |
number | The chain id, a JSON number. Send it back to ?id= as-is. Ids are not contiguous — do not iterate a range |
name |
string | The full name, e.g. "Ethereum" |
display_name |
string | A short label. Often identical to name — the Ethereum chain's is "Ethereum" — and sometimes a genuine short code: "BNB Smart Chain (BEP20)" has "BSC". Treat it as a label: it is not a lookup key here and not a sort key |
slug |
string | Unique upstream — a single slug is a single-row lookup |
evm_chain_id |
number or null |
EIP-155's chain id — what eth_chainId returns, 1 for Ethereum mainnet, 56 for BSC. A number, because that is what every EVM tool expects. null for a chain that is not an EVM network. This is not our id |
logo |
string | The logo of the chain's native coin — chains have no image of their own. Empty string when the chain has no native coin on file, or that coin is no longer in our directory. Never null |
Not implemented
The four explorer/token/address/transaction URL templates are not returned. We have not
looked at what they contain — they may be finished URLs, patterns with placeholders, or a
mix — and we are not publishing a field whose format we have not pinned down. The earlier
wording here asserted the mix as a fact; it was never measured, and the snapshot that would
have to carry that measurement says so. Also not returned: the wrapped-token reference, the
internal status flag, rank, tvl, and volume change percentages — the reasons are
/categories'.
Examples
# Default listing: 20 chains, biggest market cap first
curl -H "X-Api-Key: <your-api-key>" \
"https://open-api.coinworldcap.com/openapi/v1/chains"
# One chain by slug
curl -H "X-Api-Key: <your-api-key>" \
"https://open-api.coinworldcap.com/openapi/v1/chains?slug=ethereum"
# Several chains by id
curl -H "X-Api-Key: <your-api-key>" \
"https://open-api.coinworldcap.com/openapi/v1/chains?id=1,42"
# Show the response headers, including X-Request-Id
curl -i -H "X-Api-Key: <your-api-key>" \
"https://open-api.coinworldcap.com/openapi/v1/chains?limit=1"
Anything other than a 200 is in Errors, which covers every endpoint here.