A new feature is available for our Wallet as a Service product. 😉

Add optional custom notes to the transaction requests you make. Define reasons or details for these transactions so that the team members approving them will know exactly what they are intended for. 📋

View your notes in the Transactions Approval section in your Crypto APIs Dashboard 2.0. Add them through the Dashboard or the API itself. 👍

Another security layer for your Crypto APIs account is now a fact. 🤩

A new update in our system makes sure to send emails to account owners each time there is a successful login for their account, and moreover - if there has been a failed login attempt, too. 😎

Now you can take a breather and relax knowing that you will always be notified for your account logins. In the email notifications we return data such as the time, IP, country and location when the login attempt happened. 🤓

If you ever doubt the logins you see happening to your account, we recommend activating Two-Factor Authentication and changing your password. 👍

Now you can receive various Callbacks when using our Wallet as a Service endpoints. 👨‍🔧

Now you can make sure you are properly informed of your transaction's processes and statuses. Set up the Callback functionality and get notified by Crypto APIs for:

• every approval and/or rejection for one and the same transaction request;
• approved transaction is broadcasted;
• approved transaction is mined;
• approved transactions has failed (for some reason).

See our Developers Page here and expect more updates on Crypto APIs products here. 🙃🤓

It has not been that long just yet but Version 2.0, our APIs and new website have already proven an average execution time of 25 milliseconds! 😱 The new Crypto APIs 2.0 website alone has a 9️⃣9️⃣% speed check according to Google ‼  

Don't mind us, we're just bragging. 🧐😁 If you like what you read, though, you can always visit us at cryptoapis.io. 🤗

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.

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.