This API specific FAQ outlines answers to common questions about the CoinMarketCap API product. For questions around CoinMarketCap's general data gathering and reporting conventions, please check out the CoinMarketCap FAQ.
A: The CoinMarketCap API is our enterprise-grade cryptocurrency API for all crypto data use cases from personal, academic, to commercial. The API is a suite of high-performance RESTful JSON endpoints that allow application developers, data scientists, and enterprise business platforms to tap into the latest raw and derived cryptocurrency and exchange market data as well as years of historical data. This is the same data that powers coinmarketcap.com which has been opened up for your use cases.
A:The CoinMarketCap Developer portal is the central account management portal for your API Key and optional subscription plan while using the API. Outside of viewing the API Documentation and FAQ, you can self-provision your API Key, change and upgrade your plan, manage billing, view your daily and monthly usage, audit your API request logs, and manage account level configuration like notifications.
A:CoinMarketCap is committed to always providing the crypto community with a robust free API through our free Basic tier. Even on free Basic our users can benefits from enterprise grade infrastructure, documentation, and flexibility. If your needs outgrow our free offering check out our commercial use and enterprise offerings.
A:The API surfaces all current and historical cryptocurrency and exchange data available on coinmarketcap.com since it originally went live in 2013. See the general CoinMarketCap FAQ for listing criteria and considerations.
A:Most endpoints update every 1 minute. The update frequency for each endpoint is outlined in the endpoint's description in our API Documentation.
A: The API supports displaying market pricing data in 93 different fiat currencies as well as 4 precious metals so we likely do. You can view the full list of supported currencies in our API documentation here. This list can be fetched programmatically using our fiat map endpoint.
A: All of our historical market data is available over API and that is the preferred delivery method for many of our customers. If you prefer a custom one-time export of historical data this can be arranged using the full scope of our historical records dating back to 2013. You can inquire for custom CSV delivery pricing.
A:Our historical cryptocurrency data goes back to 2013.
You can list all active and inactive cryptocurrencies using our cryptocurrency map endpoint. You can list all active and inactive exchanges using our exchange map endpoint. Each cryptocurrency and exchange returned from these endpoints include a "first_historical_data" timestamp letting you know how far our historical records go back.
A:Yes, our /cryptocurrency/info and /exchange/info metadata endpoints include hosted logo assets in PNG format. 64px is the default size returned but you may replace "64x64" in the image path with these alternative sizes: 16, 32, 64, 128, 200.
A:You should consider an enterprise plan if you need higher API call credit and rate limits, access to more historical data, a custom license outside of our standard commercial agreement and/or a Service Level Agreement.
A:You can check the expanded feature matrix on the API Plan Feature Comparison page. The API documentation also outlines what plans support what API endpoints, just look under the description field for any particular endpoint. If you're still unsure, feel free to reach out to us at firstname.lastname@example.org.
A:We have a testing sandbox available at sandbox.coinmarketcap.com where you can create test accounts to trial any of our subscription tiers with real data. The data available in this sandbox is limited but convenient enough for most testing purposes. Feel free to sign up for an account and test, then switch over to coinmarketcap.com/api when ready.
A:As the API offers enterprise level pagination, usage is tracked not by amount of API calls, but by number of data points returned. This is typically 1 "call credit" per 100 data points returned unless otherwise specified in endpoint documentation. A more detailed outline of this system can be found in our API documentation.
Our plan features page outlines the maximum number of call credits that can be consumed each day and month at each tier. These are outlined as soft caps and hard caps. Soft caps are suggested limits that can give you some room before you reach your hard limit for the period. Period limits reset either at the end of each UTC day and month, or in-sync with a paid plan's monthly subscription cycle. You can click the "?" on your API Credit Usage panel for these details specific to your API key.
A: This is the number of HTTP calls that can be made simultaneously or within the same minute with your API Key before receiving an HTTP 429 "Too Many Requests" API throttling error. This limit increases with the usage tier and resets every 60 seconds. Please review our best practices for implementation strategies that work well with rate limiting.
A: Yes! For your convenience we notify you by email when your API key reaches above 95% of daily/monthly credit usage limits. You may disable these notifications or configure additional alerts via your account notifications page.
A: API plans feature a daily limit ("soft cap") and monthly limit ("hard cap") to the number of data calls that can be made. This daily limit email is just a friendly warning that based on your daily credit usage, you run the high risk of hitting your monthly hard limit before the monthly reset.
Period limits reset either at the end of each UTC day and month, or in-sync with a paid plan's monthly subscription cycle. You can click the "?" icon on your API Credit Usage panel for details specific to your plan.
If hitting your monthly credit limit prematurely concerns you, you can upgrade your plan for more credits, otherwise you may ignore or even disable this warning. Supported plans may also enable Overage Billing, see below.
A: Enable overage billing to prevent your API requests from being blocked if you happen to exceed your plan's daily or monthly API credit usage limits.
At the end of each billing period, we'll include an overage charge for any credit usage above your standard monthly limit using your plan's standard cost-per-credit rate.
Enable or disable this feature by toggling the "Enable overage billing" checkbox under "Subscription Details" on the Plan & Billing tab. Overage billing is currently only supported by monthly credit card subscriptions.
A:As a premier data authority for exchange market data, we are actively working with every exchange to ensure their data is not only available to us, but also available to you over the new API service. You may see this notice when market data for an exchange is in our system but not yet available over the API. There are only a handful left to confirm and this notice may all but disappear over the upcoming weeks. In the meantime a -1 response means the exchange's data is not yet available over API.
A: Service disruptions are rare but reported on our public API health dashboard. You may subscribe to updates using the button on that page.
A:Customers on paid plans can expect to receive answers within 24 hours.
A: We roll out new enhancements to the API monthly. Customers who are already subscribed to a plan automatically gain access to these new features. Ensure you're subscribed to the API Newsletter to receive updates. You can also reference our Version History which is updated with every release.
A:We'd be happy to assist with any account servicing needs. Please reach out to email@example.com.
A:We'd love to get your question answered and added to the API Documentation or this FAQ. You can reach out to us at firstname.lastname@example.org and we'll get back to you as soon as we can.