We are happy to finally announce the release of the new Crypto APIs 2.0!
It incorporates a better and more efficient architecture that allows blockchain enthusiasts and entrepreneurs alike to use a wide range of specialized features and tools to create their crypto solutions.
The diverse subscription plans and the arrangement of functionalities among them was carefully calculated to be of use to both the novice Bitcoin/Ethereum devotee and the professional.
By using Blockchain Data, Blockchain Events, Blockchain Automations and Blockchain Tools, you practically have everything to easily develop new, or quickly improve your existing blockchain and crypto applications.
We are happy to announce that we have finished the stress tests on Crypto APIs 2.0, and the results are amazing.
We have achieved a 25 ms response time for 10,000 requests per second, which is a huge success comparing with current APIs on the market.
Crypto APIs 2.0 is OpenAPI 3.0 based.
Please stay tuned for further updates!
ETH Payments Forwarding was optimized successfully. We had issues because of the huge number of forwarding we do.
After the done optimization, we could process hundreds of thousands of forwarding per day without any delay.
Sending transactions in HD wallets was not selecting the UTXOs properly.
This issue is fixed now and you can rely on our HD wallet and send transaction endpoint to avoid building the transaction, checking UTXOs, etc.
The new menu under your Dashboard allows you to download your invoices, track your payment history; sort by date, amount, and purchased plan.
Now you can set the new optional parameter "everyConfirmation" to true, this means you want to get a callback for every confirmation, of course these callbacks stop when they reach "confirmations".
As you may know BCH has legacy addresses and new format which starts with "bitcoincash:"
In Crypto APIs, we support both in all endpoints but when you subscribe for a webhook for a legacy address and there is a transaction for the same address but with the new format we didn't send you a callback.
Now, we send you a callback for such transactions as well and to avoid any confusing on your side we send the "originalAddress" in the response.
Here you can see all details: https://docs.cryptoapis.io/rest-apis/blockchain-as-a-service-apis/bch/index#webhook-notifications
You can't create the same webhook more than once now, in order to create exactly the same webhook event you need to set the optional parameter "allowDuplicate" to true, this will allow you to add as much as you want the same webhook event.