PUT /user/tokenGET /wallet/:wallet_name/balance now accepts a query parameter currency. Passing currency will return balance for currency in a wallet. If not given, will return balance for default wallet currency. currency as xht will return xht balance in eth walletcurrency will return eth balance in eth walletnetworkdin query parameter to handle status check of transaction on specific blockchain network.GET /wallet/:wallet_name/balancecurrency that specifies which currency to get balance for.network /wallet/{wallet_name}/withdraw/simple/wallet/{wallet_name}/withdraw is using the same body format as /wallet/{wallet_name}/withdraw/simple starting from v1.14 release. It uses an object instead of array using the format below:/wallet/{wallet_name}/address is deprecated and instead /wallet/{wallet_name}/address/new should be used./wallet/{wallet_name}/withdraw/simpleand /wallet/{wallet_name}/address endpoint will no longer be supported after v1.15 so you need to change it as soon as possible to avoid any issues in future.fee and min are added to POST /sweep to allow advance customization of sweeping. fee by default was always set to minimum fee on the chain and min was set to 0 previously. Now minimum amount can be specified with the sweeping fee in order to hand pick large transactions without them getting stuck in the blockchain due to low fees.https://api.bitholla.com to https://api.vault.bitholla.com/vault changed to /wallet for most endpoints (details listed below)https://api.bitholla.com => https://api.vault.bitholla.comGET /vault/coins => GET /coinsGET /vault/:wallet_name/check => GET /wallet/:wallet_name/checkPOST /vault/wallet => POST /walletDELETE /vault/wallet => DELETE /walletGET /vault/user/wallets => GET /user/walletsGET /vault/:wallet_name/master => GET /wallet/:wallet_name/masterGET /vault/:wallet_name/address/new => GET /wallet/:wallet_name/address/newGET /vault/:wallet_name/addresses => GET /wallet/:wallet_name/addressesGET /vault/:wallet_name/balance => GET /wallet/:wallet_name/balanceGET /vault/:wallet_name/restart => GET /wallet/:wallet_name/restartPOST /vault/:wallet_name/withdraw => POST /wallet/:wallet_name/withdrawPOST /vault/:wallet_name/withdraw/simple => POST /wallet/:wallet_name/withdraw/simplePOST /vault/:wallet_name/withdraw/batch => POST /wallet/:wallet_name/withdraw/batchPUT /vault/:wallet_name/sweep => PUT /wallet/:wallet_name/sweepPOST /vault/:wallet_name/sweep => POST /wallet/:wallet_name/sweepGET /vault/:wallet_name/transactions => GET /wallet/:wallet_name/transactionsGET /vault/transaction/status => GET /wallet/transaction/statusPUT /vault/:wallet_name/webhook => PUT /wallet/:wallet_name/webhookGET /vault/:wallet_name/webhook/test => GET /wallet/:wallet_name/webhook/testPOST /vault/webhook/test to GET /vault/:wallet_name/webhook/test:wallet_name)POST /vault/webhook/test => GET /vault/:wallet_name/webhook/testPUT /vault/:wallet_name/sweepauto_sweep auto_sweep set to true will be swept by vault every ~5 minutesauto_sweep set to false by defaultPOST /vault/:wallet_name/sweepaddressaddressGET /vault/:wallet_name/restartPUT /vault/:wallet_name/sweepPOST /vault/:wallet_name/sweepGET /vault/:wallet_name/restartGET /vault/:wallet_name/transactionstxid query filter that filters result by transaction idDELETE /vault/walletwallet_id) in the request bodyPOST /vault/{wallet_name}/withdraw/simplePOST /vault/{wallet_name}/withdraw but with better body data structurePOST /vault/{wallet_name}/withdraw/batchBTC and BCHdata which is an array of objects with the individual withdrawal addresses and amounts and an optional fee. POST /vault/{wallet_name}/withdraw/simplePOST /vault/{wallet_name}/withdraw/batchDELETE /vault/walletGET /vault/{wallet_name}/address/newGET /vault/{wallet_name}/addressPOST /vault/wallettype field to body object that specifies the type of wallet being created. Can be one of single or multi. Default value is multi. GET /vault/{wallet_name}/addressGET /vault/{wallet_name}/address/newGET /vault/{wallet_name}/check.GET /vault/coins. GET /vault/user/wallets now has a name query parameter. Vault will return all wallets with names that include the name value.GET /vault/{wallet_name}/check GET /vault/coins GET /vault/user/walletsname query parametermeta tag of POST /vault/{wallet_name}/withdraw, there is an added field called fee where users can choose to add an optimal, low, or min optimal: Recommended fee required to make the withdrawallow: Low priority feemin: Lowest possible feeoptimal fee if users don't add a fee fieldoptimal fee.amount field in the body of a POST /vault/{wallet_name}/withdraw request is now optional. To withdraw the total amount in the wallet, either omit the amount field or set it as 0. GET /vault/{wallet_name}/transactions now takes an address query parameter. Set this parameter as an address to filter the request.is_rejected field has been added to transactions which indicates whether or not the transaction was rejected by the blockchain./v0 updated to /v1/v0 is still supported but users should use /v1 going forward.POST /vault/{wallet_name}/withdrawfee field in the meta tag where users can choose a withdrawal fee.amount field is now optional and can be omitted or set to 0 to indicate a maximum withdrawal.GET /vault/{wallet_name}/transactionsaddress query parameter that filters transactions by address./vault/transaction/status && /dash/vault/transaction/statusis_testnet. It is a boolean variable and specifies if the transaction being checked was on the testnet or not. The default value is false.vault/webhook/testis_testnet field that specifies if the transaction being checked was on the testnet or not. The default value is false.meta attribute to the body being sent withPOST /vault/:wallet_name/withdraw . It is an optional attribute that is an object where a user can send additional variables with a withdraw request. For example, XRP withdrawals require a tag value. Users can send this tag within the meta attribute.GET request to /vault/transaction/status with the currency, transaction_id, and address of the deposit as query parameters. Vault will check the blockchain to confirm the deposit and sweep the funds to the master address.GET /vault/{wallet_name}/master wallet_nameGET /vault/{wallet_name}/balance wallet_nameGET /vault/transaction/statuscurrency, transaction_id, address required.api-key and api-secret are now called key and secret, respectively. They are still required in the header for authorization purposes. POST /vault/{wallet_name}/withdrawcurrency is no longer required in the JSON object.