cryptoCMD: cryptoCurrency Market Data
Cryptocurrency historical market price data scraper written in Python.
Installation
pip install cryptocmd
to install from the latest source use following command
pip install git+git://github.com/guptarohit/cryptoCMD.git
Usage
CoinMarketCap Scraper
Following methods are available to get data in multiple formats from https://coinmarketcap.com
To get all time historical data of a cryptocurrency
from cryptocmd import CmcScraper
# initialise scraper without time interval
scraper = CmcScraper("XRP")
# get raw data as list of list
headers, data = scraper.get_data()
# get data in a json format
xrp_json_data = scraper.get_data("json")
# export the data as csv file, you can also pass optional `name` parameter
scraper.export("csv", name="xrp_all_time")
# Pandas dataFrame for the same data
df = scraper.get_dataframe()
To get data of a cryptocurrency which have same coin code as others
from cryptocmd import CmcScraper
# initialise scraper with coin name as well
scraper = CmcScraper(coin_code="sol", coin_name="solana")
# get raw data as list of list
headers, data = scraper.get_data()
# get data in a json format
solana_json_data = scraper.get_data("json")
# export the data as csv file, you can also pass optional `name` parameter
scraper.export("csv", name="solana_all_time")
# Pandas dataFrame for the same data
df = scraper.get_dataframe()
To get data of a cryptocurrency for some days
from cryptocmd import CmcScraper
# initialise scraper with time interval
scraper = CmcScraper("XRP", "15-10-2017", "25-10-2017")
# get raw data as list of list
headers, data = scraper.get_data()
# get data in a json format
json_data = scraper.get_data("json")
# export the data to csv
scraper.export("csv")
# get dataframe for the data
df = scraper.get_dataframe()
Following are the columns of the data
Date, Open, High, Low, Close, Volume, Market Cap, Time Open, Time High, Time Low, Time Close
Acknowledgements
The data is being scrapped from coinmarketcap :v: and it's free to use. :tada:
Contributing
Feel free to make a pull request! :octocat:
If you found this useful, I'd appreciate your consideration in the below. ✨☕
Metadata
Release files for cryptocmd 0.6.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cryptocmd-0.6.5.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cryptocmd-0.6.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.0 kB
Release files / cryptocmd-0.6.5.tar.gz
| Download URL | cryptocmd-0.6.5.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3037d134b37dfb59e46b9edf1bad197b76827c503388b38ee4d9bcf503c25554
|
|
BLAKE2b-256 checksum How to use checksums |
a94db8fb54cef99e9456d1009c01a1a14694e1729420de5110d252770701befb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logRelease files / cryptocmd-0.6.5-py3-none-any.whl
| Download URL | cryptocmd-0.6.5-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be813823cd6f9a0ac7ad8fc255dbe7bbb24f906b3be3cb6bfcfc7a9b7f422d05
|
|
BLAKE2b-256 checksum How to use checksums |
853d58464e8f18dd5c68b274dcd6f0b8df8366bb670a7dc281b30b2d20bda4bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency log