CoinMarketCapCoinMarketCap
PricingAPI StatusGet an API Key

© 2026 CoinMarketCap. All rights reserved.

xgithub
  • Overview
  • API Reference
  • AI Agent Hub
  • Changelog
  • FAQ
Start Here
    API OverviewQuick StartAuthenticationCommon Workflows
Using the API
    Standards and ConventionsRate limits and troubleshootingBest Practices
Using the API

Standards and Conventions

Each HTTP request must contain the header Accept: application/json. You should also send an Accept-Encoding: deflate, gzip header to receive data fast and efficiently.

Endpoint Response Payload Format

All endpoints return data in JSON format with the results of your query under data if the call is successful.

A Status object is always included for both successful calls and failures when possible. The Status object always includes the current time on the server when the call was executed as timestamp, the number of API call credits this call utilized as credit_count, and the number of milliseconds it took to process the request as elapsed. Any details about errors encountered can be found under the error_code and error_message. See Rate limits, errors, and troubleshooting for details on errors.

Code
{ "data" : { ... }, "status": { "timestamp": "2018-06-06T07:52:27.273Z", "error_code": 400, "error_message": "Invalid value for \"id\"", "elapsed": 0, "credit_count": 0 } }

Cryptocurrency, Exchange, and Fiat currency identifiers

  • Cryptocurrencies may be identified in endpoints using either the cryptocurrency's unique CoinMarketCap ID as id (eg. id=1 for Bitcoin) or the cryptocurrency's symbol (eg. symbol=BTC for Bitcoin). For a current list of supported cryptocurrencies use /cryptocurrency/map.
  • Exchanges may be identified in endpoints using either the exchange's unique CoinMarketCap ID as id (eg. id=270 for Binance) or the exchange's web slug (eg. slug=binance for Binance). For a current list of supported exchanges use /exchange/map.
  • All fiat currency options use the standard ISO 4217 currency code (eg. USD for the US Dollar). For a current list of supported fiat currencies use /fiat/map. Unless otherwise stated, endpoints with fiat currency options like our convert parameter support these 93 major currency codes:
CurrencyCurrency CodeCoinMarketCap ID
United States Dollar ($)USD2781
Albanian Lek (L)ALL3526
Algerian Dinar (د.ج)DZD3537
Argentine Peso ($)ARS2821
Armenian Dram (֏)AMD3527
Australian Dollar ($)AUD2782
Azerbaijani Manat (₼)AZN3528
Bahraini Dinar (.د.ب)BHD3531
Bangladeshi Taka (৳)BDT3530
Belarusian Ruble (Br)BYN3533
Bermudan Dollar ($)BMD3532
Bolivian Boliviano (Bs.)BOB2832
Bosnia-Herzegovina Convertible Mark (KM)BAM3529
Brazilian Real (R$)BRL2783
Bulgarian Lev (лв)BGN2814
Cambodian Riel (៛)KHR3549
Canadian Dollar ($)CAD2784
Chilean Peso ($)CLP2786
Chinese Yuan (¥)CNY2787
Colombian Peso ($)COP2820
Costa Rican Colón (₡)CRC3534
Croatian Kuna (kn)HRK2815
Cuban Peso ($)CUP3535
Czech Koruna (Kč)CZK2788
Danish Krone (kr)DKK2789
Dominican Peso ($)DOP3536
Egyptian Pound (£)EGP3538
Euro (€)EUR2790
Georgian Lari (₾)GEL3539
Ghanaian Cedi (₵)GHS3540
Guatemalan Quetzal (Q)GTQ3541
Honduran Lempira (L)HNL3542
Hong Kong Dollar ($)HKD2792
Hungarian Forint (Ft)HUF2793
Icelandic Króna (kr)ISK2818
Indian Rupee (₹)INR2796
Indonesian Rupiah (Rp)IDR2794
Iranian Rial (﷼)IRR3544
Iraqi Dinar (ع.د)IQD3543
Israeli New Shekel (₪)ILS2795
Jamaican Dollar ($)JMD3545
Japanese Yen (¥)JPY2797
Jordanian Dinar (د.ا)JOD3546
Kazakhstani Tenge (₸)KZT3551
Kenyan Shilling (Sh)KES3547
Kuwaiti Dinar (د.ك)KWD3550
Kyrgystani Som (с)KGS3548
Lebanese Pound (ل.ل)LBP3552
Macedonian Denar (ден)MKD3556
Malaysian Ringgit (RM)MYR2800
Mauritian Rupee (₨)MUR2816
Mexican Peso ($)MXN2799
Moldovan Leu (L)MDL3555
Mongolian Tugrik (₮)MNT3558
Moroccan Dirham (د.م.)MAD3554
Myanma Kyat (Ks)MMK3557
Namibian Dollar ($)NAD3559
Nepalese Rupee (₨)NPR3561
New Taiwan Dollar (NT$)TWD2811
New Zealand Dollar ($)NZD2802
Nicaraguan Córdoba (C$)NIO3560
Nigerian Naira (₦)NGN2819
Norwegian Krone (kr)NOK2801
Omani Rial (ر.ع.)OMR3562
Pakistani Rupee (₨)PKR2804
Panamanian Balboa (B/.)PAB3563
Peruvian Sol (S/.)PEN2822
Philippine Peso (₱)PHP2803
Polish Złoty (zł)PLN2805
Pound Sterling (£)GBP2791
Qatari Rial (ر.ق)QAR3564
Romanian Leu (lei)RON2817
Russian Ruble (₽)RUB2806
Saudi Riyal (ر.س)SAR3566
Serbian Dinar (дин.)RSD3565
Singapore Dollar (S$)SGD2808
South African Rand (R)ZAR2812
South Korean Won (₩)KRW2798
South Sudanese Pound (£)SSP3567
Sovereign Bolivar (Bs.)VES3573
Sri Lankan Rupee (Rs)LKR3553
Swedish Krona ( kr)SEK2807
Swiss Franc (Fr)CHF2785
Thai Baht (฿)THB2809
Trinidad and Tobago Dollar ($)TTD3569
Tunisian Dinar (د.ت)TND3568
Turkish Lira (₺)TRY2810
Ugandan Shilling (Sh)UGX3570
Ukrainian Hryvnia (₴)UAH2824
United Arab Emirates Dirham (د.إ)AED2813
Uruguayan Peso ($)UYU3571
Uzbekistan Som (so'm)UZS3572
Vietnamese Dong (₫)VND2823

Along with these four precious metals:

Precious MetalCurrency CodeCoinMarketCap ID
Gold Troy OunceXAU3575
Silver Troy OunceXAG3574
Platinum OunceXPT3577
Palladium OunceXPD3576

Warning: Using CoinMarketCap IDs is always recommended as not all cryptocurrency symbols are unique. They can also change with a cryptocurrency rebrand. If a symbol is used the API will always default to the cryptocurrency with the highest market cap if there are multiple matches. Our convert parameter also defaults to fiat if a cryptocurrency symbol also matches a supported fiat currency. You may use the convenient /map endpoints to quickly find the corresponding CoinMarketCap ID for a cryptocurrency or exchange.

Bundling API Calls

  • Many endpoints support ID and crypto/fiat currency conversion bundling. This means you can pass multiple comma-separated values to an endpoint to query or convert several items at once. Check the id, symbol, slug, and convert query parameter descriptions in the endpoint documentation to see if this is supported for an endpoint.
  • Endpoints that support bundling often return data as an object map instead of an array, especially in v1 quote and info style endpoints. Newer versions may return arrays instead, so always confirm the response shape in the endpoint reference.

For example, if you passed symbol=BTC,ETH to /v1/cryptocurrency/quotes/latest you would receive:

Code
"data" : { "BTC" : { ... }, "ETH" : { ... } }

Or if you passed id=1,1027 you would receive:

Code
"data" : { "1" : { ... }, "1027" : { ... } }

Price conversions that are returned inside endpoint responses behave in the same fashion. These are enclosed in a quote object.

Date and Time Formats

  • All endpoints that require date/time parameters allow timestamps to be passed in either ISO 8601 format (eg. 2018-06-06T01:46:40Z) or in Unix time (eg. 1528249600). Timestamps that are passed in ISO 8601 format support basic and extended notations; if a timezone is not included, UTC will be the default.
  • All timestamps returned in JSON payloads are returned in UTC time using human-readable ISO 8601 format which follows this pattern: yyyy-mm-ddThh:mm:ss.mmmZ. The final .mmm designates milliseconds. Per the ISO 8601 spec the final Z is a constant that represents UTC time.
  • Data is collected, recorded, and reported in UTC time unless otherwise specified.

Versioning

The CoinMarketCap API is versioned to guarantee new features and updates are non-breaking. The current documentation includes v1, v2, and v3 endpoints depending on the product area. Always use the version shown on the endpoint you are integrating.

Common WorkflowsRate limits and troubleshooting
JSON
JSON
JSON