GitHub, Google and LinkedIn direct registration/login was implemented in Crypto APIs dashboard.
GitHub, Google and LinkedIn direct registration/login was implemented in Crypto APIs dashboard.
You can activate 2 factor authentication in your dashboard, it's highly recommended to make your account safe and secure.
When you call an endpoint to get transactions by address in BCH you can use the legacy address or the new format, if you use the legacy you will get the transactions as legacy however if you use the new format you will get the transactions in the new format.
The same is valid for Get Unconfirmed Transactions By Address as well:
You can now get the token transfers by address by Token Type (e.g "ERC-20" or "ERC-721"):
You can now get the token transactions by address by token type (e.g "ERC-20" or "ERC-721"):
The endpoint now supports limit and index, it's highly recommended to take the data in small portions. The default results number is the same as for all endpoints: 50.
Get Token Transactions By Address: https://docs.cryptoapis.io/rest-apis/blockchain-as-a-service-apis/eth/index#eth-get-address-token-transactions
Sending a transaction using HD wallet was giving sometimes an error like: "Total inputs(x) amount should be equal to total outputs(xx) amount!" which means that it has no funds but in fact there are enough funds distributed between the different addresses.
The issue is fixed now, when you use HD wallet sending transactions Crypto APIs will take care of inputs.
To know what fee you should set, use HD wallet size endpoint and fee per size.
To be able to calculate the fee properly you would need to know the size of your transaction in bytes, to do that you can use this endpoint: https://docs.cryptoapis.io/rest-apis/blockchain-as-a-service-apis/btc/index#btc-transactions-size
Now you can use it without sending the fee itself.
You can change your email in your dashboard now: https://dashboard.cryptoapis.io/account/change-email
In case you are using HD wallets and you wonder what fee to set, you can now use this endpoint:
The value you get is the size in bytes, to define the fee you would need to multiply it by "minfeeperbyte", "averagefeeperbyte" or "maxfeeper_byte" from our transaction fee endpoint: