crypto_vba VS VBA-JSON

Compare crypto_vba vs VBA-JSON and see what are their differences.


JSON conversion and parsing for VBA (by VBA-tools)
Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Less time debugging, more time building
  • SaaSHub - Software Alternatives and Reviews
crypto_vba VBA-JSON
4 9
143 1,211
- 2.0%
0.6 0.0
11 months ago 5 months ago
VBA Visual Basic
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of crypto_vba. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-10.
  • VBA API call with nested JSON data
    2 projects | | 10 Dec 2021
    It basically uses the Dictionary object to create variables (e.g. with a dictionary in a dictionary) and after that using that library to transform it into a string. I'm using it in my project here:
  • Where should I store API Keys?
    1 project | | 9 Dec 2021
    I agree with u/sslinky84 that there is no safe place in VBA. The main question is: what's the purpose of an API key in this case? From your description you are not linking an API-key to a single user, but have "one key to rule them all". So you probably want to prevent someone from grabbing your end-point and spamming it? In that case you're perfectly fine in creating one API-string in VBA and checking that on the server: it blocks the person who is opening a browser to fiddle with your end-point, but it does give you some security. The people who can get through are the ones that manage to crack open your VBA (assuming you have a password on the VBA). To make their life a bit harder you could instead of a "fixed string" as API key go for some kind of hash, as u/archn suggests. E.g.: take the rest of the post message that e.g. also includes a mandatory timestamp, make a simple hash of that (might even include a "fixed key", see e.g. for some code).
  • Self made Excel/VBA triggers virus scan - what to do?
    1 project | | 19 Mar 2021
    I've built an open source VBA-Excel library to communicate with cryptocurrency exchanges ( ) and have my code available as .bas and in an .xlsm file. A couple of days ago someone posted an issue that my xlsm file triggered a Windows defender alert. At my pc this doesn't happen, the AVG virus scanner also won't show anything.
  • How to import price actions with API from CoinGecko
    1 project | | 16 Feb 2021
    I am mainly using Cryptocompare, but if you want to use CoinGecko, check out my code, it has the basics: It has most of the essentials: connecting Excel to web, handling Json and some API examples.


Posts with mentions or reviews of VBA-JSON. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-10.

What are some alternatives?

When comparing crypto_vba and VBA-JSON you can also consider the following projects:

crypto-trading-bot - Cryptocurrency trading bot in javascript for Bitfinex, Bitmex, Binance, FTX, Bybit ... (public edition)

VBA-JSON-parser - Backus-Naur Form JSON Parser based on RegEx for VBA

Export-MS-Project-to-MS-Excel - Export tasks, Gantt chart and resources from MS Project to MS Excel. No additional software or installation required. Using build-in MS Project features (VBA).

QueryCsvToExcel - Provides VBA code for executing a SQL query on a CSV file to import data into a worksheet in Excel

coinbasepro-python - The unofficial Python client for the Coinbase Pro API

cryptofeed - Cryptocurrency Exchange Websocket Data Feed Handler

ccxws - WebSocket client for 38 cryptocurrency exchanges