What's New

August 11, 2022
API v3.14.0
Ethereum: Get Notified when Transaction Appears in Mempool
Great news for our Ethereum users: you can now use the ADDRESS_TRANSACTION and ACCOUNT_PENDING_BLOCKCHAIN_TRANSACTION notification subscriptions to get notified when a transaction related to your Ethereum blockchain address or ETH virtual account appears in the mempool.
This will help you find out about such transactions before they get added to a block.
What are these subscription types for, anyway?
A subscription of the ADDRESS_TRANSACTION type sends a notification about any transaction (incoming or outgoing) at a specified blockchain address.
A subscription of the ACCOUNT_PENDING_BLOCKCHAIN_TRANSACTION type sends a notification about incoming transactions on a virtual account.
What exactly changed for these subscription types?
When you set up an ADDRESS_TRANSACTION subscription for an Ethereum address, a notification will now be sent to you as soon as a transaction made from/to your address hits the mempool.
The body of such notification includes a new parameter, mempool, set to true, which means that the transaction has been detected in the Ethereum mempool:
{
  "address": "0x9WNce4e40889a13971681391AAd29E88eFAF91f7",
  "txId": "0x45af182a0ffab58e5ba32...c76c7ee22d72dea99",
  "asset": "ETH",
  "amount": "0.00004",
  "mempool": true,
  "type": "native",
  "counterAddress": undefine
}
Notice that the blockNumber parameter is not present in the notification because the transaction has not been added to any block yet.
Once the transaction is added to a block, another notification will be sent. This notification is not going to have the mempool parameter, but it will include the number of the block where the transaction was recorded into.
NOTE: Nothing has changed for ADDRESS_TRANSACTION subscriptions for the other supported blockchains: for them, a notification is still sent when a transaction is added to a block.
When you set up an ACCOUNT_PENDING_BLOCKCHAIN_TRANSACTION subscription for a virtual account in ETH, a notification will now be sent to you as soon as a transaction to your virtual account hits the mempool.
In the body of such notification, the blockHash and blockHeight parameters are set to null because the transaction has not been added to any block yet:
{
  "date": 1619176527481,
  "amount": "0.0005",
  "currency": "ETH",
  "accountId": "1124vb946371b0047825c6a0",
  "reference: "c9875708-4ba3-41c9-a4cd-271048b41b9a",
  "txId": "0x45af182a0ffab58e5ba32...c76c7ee22d72dea99",
  "blockHash": null,
  "blockHeight": null,
  "from": "0xFykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXw"
  "to": "0x9WNce4e40889a13971681391AAd29E88eFAF91f7",
  "index": null
}
The virtual account balance, however, will not be updated until the transaction is added to a block. Instead, a deposit corresponding to the pending transaction with a status of "in progress" will appear on the virtual account.
Once the transaction is added to the block, the deposit's status will change to "done", and the account balance will be credited with the transaction amount. If you want to get a notification about the balance update, create a subscription of the ACCOUNT_INCOMING_BLOCKCHAIN_TRANSACTION type.
NOTE: Nothing has changed for ACCOUNT_PENDING_BLOCKCHAIN_TRANSACTION subscriptions for the other supported blockchains: for them, a notification is still sent when a transaction appears in a block for the first time.
Need more information about the subscriptions?
Please refer to our API Reference and the following articles:
​How to monitor transactions at any address​
​How to automatically scan blockchain addresses and set up webhook notifications​
Ethereum: Sepolia Replaced Rinkeby and Ropsten
Following the deprecation of the Rinkeby and Ropsten support, we dropped both Rinkeby and Ropsten completely.
From now on, Sepolia is the default Ethereum testnet.
What does it mean?
Any API call explicitly made toward Rinkeby or Ropsten will either fail with a validation error (no endpoint found) or be automatically redirected to Sepolia and return the requested data from Sepolia instead of Rinkeby or Ropsten.
For example, requesting the number of the latest block on Ropsten will return the number of the latest block on Sepolia.
You cannot access any of your data on Ropsten or Rinkeby such as NFTs, smart contracts, or transactions. However, you can still reuse your existing addresses and private keys as well as notifications attached to the addresses on Sepolia. Virtual accounts and subscriptions attached to them remain under your API key but reference Sepolia.
How can you adopt the changes?
Consider migrating your projects to Sepolia.
Redeploy your smart contracts on Sepolia.
Check whether your code references Rinkeby and/or Ropsten. If so, update it to either rely on the Tatum API to choose the testnet for you, or point to Sepolia explicitly.
Need more information about the Ethereum testnets?
Please refer to the Ethereum deprecation announcement and the Ethereum user documentation.
Fantom: New Blockchain Available via RPC
We have added Fantom to the list of the blockchains to which you can connect directly via the node provided by Tatum:
https://{region}.tatum.io/v3/blockchain/node/FTM/{your_api_key}/{rpc_path}
For more information about Fantom RPCs, please refer to the Fantom user documentation.
​
July 22, 2022
KMS v5.0
Key Management System: Version 5.0 Available
We released version 5.0 of our Key Management System (KMS). KMS is a comprehensive security solution that generates and stores private keys and uses them to sign transactions locally.
KMS version 5.0 brings improved performance: it can take up to 25,000 signature IDs in one go, which means more transactions get signed and sent out to a blockchain for further processing.
To download or upgrade KMS, please visit our GitHub page. To learn how to use KMS, see this article.
​
API v3.13.0
Ethereum: Sepolia Replaces Rinkeby and Ropsten
Following the Ethereum deprecation announcement, we deprecated support for the Rinkeby and Ropsten testnets on Ethereum. We are going to drop both Rinkeby and Ropsten completely in the next release, which is planned to happen in early August. We will post a separate announcement when it happens.
When Rinkeby and Ropsten are made unavailable, Sepolia will become the default Ethereum testnet. That means that any API call made toward an Ethereum testnet will be directed to Sepolia.
Is Sepolia already available for use?
Yes. You can use Sepolia if you work with Ethereum via the blockchain node provided by Tatum. Just add the testnetType parameter to the API endpoint URL and set it to ethereum-sepolia:
https://{region}.tatum.io/v3/blockchain/node/ETH/{your_api_key}/{rpc_path}?testnetType=ethereum-sepolia
How can you get prepared?
Please check whether your code references Rinkeby and/or Ropsten. If so, prepare an update to either rely on the Tatum API to choose the testnet for you, or point to Sepolia explicitly.
TRON: Negative Number Issue in Notifications Fixed
We fixed the issue that occurred in the ADDRESS_TRANSACTION notifications sent for the native currency transactions on TRON. These are transactions where an amount in native TRON currencies (TRX, TRC-10, or TRC-20) is transferred from one address to the other. Such transactions have the type set to native in the notifications.
In such notifications, the amount sometimes was displayed as a negative number, for example:
"amount": "-2"
This has been fixed. Now, the amount in the notifications for native TRON currency transactions is always returned as a positive number.
​
June 24, 2022
API v3.12.0
Support for Blockchains Deprecated: EOSIO, Lisk, Neo, Qtum, and Terra (LUNA)
We deprecated support for the following blockchains:
EOSIO (EOS)
Lisk (LSK)
Neo (NEO)
Qtum (QTUM)
Terra (LUNA)
What does it mean?
For the specified blockchains, the blockchain-specific APIs are now marked as deprecated in the API Reference.
The blockchain-specific APIs are the APIs with the endpoint explicitly pointing to the blockchain, for example, https://{region}.tatum.io/v3/neo/... or https://{region}.tatum.io/v3/qtum/....
Those APIs are still usable, but we recommend that you stop using them. Eventually, we will disable and remove those APIs completely.
In the APIs where the specified blockchains or their assets can be used as a parameter in the request body or as a path parameter, the blockchains are no longer available in the list of available values for these parameters.
For example, EOS and LUNA are no longer listed as possible values for the currency parameter for https://{region}.tatum.io/v3/tatum/rate/{currency}.
Other than that, those APIs do not change in any way.
For EOSIO, Lisk and Terra (LUNA), you still can and will be able to connect to the blockchains directly via RPC nodes.
Need help?
If you have any question or concern regarding the deprecated blockchains, please contact Tatum Support at [email protected] or post a question in the #api channel on our Discord.
​
Dashboard v1.23.0
Dashboard: Minor Tweaks and Bug Fixes
For our Dashboard, we fixed a few bugs and made some improvements in the underlying processes. We are working on new features - please stay tuned!
If you do not have a Dashboard account yet, you can sign up here.
​
June 10, 2022
Dashboard v1.22.0
New Features on Dashboard
We added a few new features to our Dashboard. Check them out at https://dashboard.tatum.io/.
If you do not have an account yet, you can sign up here.
What’s new on the Dashboard?
The menu panel now includes the following options: 
Explore (and its underlying options)
NFT Minter
The options under Explore let you review your assets and activities:
Debug
This option has already been here before, we just moved it under Explore. Here, you can see the last 100 API calls that you made.
Deposits
This option lists the deposits that you have made and received and lets you filter them by different criteria (from, to, currency, status, and so on).
Subscriptions
This option lists your existing subscriptions and lets you create a new subscription right from the Dashboard.
Webhooks
This option lists the last 10 webhook calls that have been made based on your subscriptions, including those that failed.
Virtual Accounts
This option lists your existing virtual accounts and lets you filter them by different criteria (active/frozen, currency, customer ID, and so on).
NFT Minter allows you to mint NFTs right from the Dashboard and without the need to make API calls.
You can mint NFTs for the following blockchains:
BNB Smart Chain (BSC)
Celo (CELO)
Ethereum (ETH)
Harmony (ONE)
Klaytn (KLAY)
Polygon (MATIC)
Solana (SOL)
Please be aware of the following:
All the new features use the corresponding APIs in the background (for example, listing the webhook calls under Webhooks uses the API for listing executed webhooks). Each API call consumes a specific number of credits. Please review the API Reference to see how many credits each API consumes.
NFT Minter runs on the API for minting NFTs and uses the NFT Express feature. When used on the mainnet, NFT Express works only with paid Tatum plans: Tatum covers the minting fee for you and then deducts the corresponding number of credits from your monthly credit allowance.
​
June 3, 2022
API v3.11.0
Solana and Algorand: Get the Number of Fungible Tokens per Address
For the Solana and Argoland blockchains, you can now retrieve the number of fungible (ERC-20 equivalent) tokens that a specific blockchain address holds.
To do so, use the API for getting ERC-20 tokens per address, and make sure to replace the chain path parameter with either SOL  or ALGO.
https://{region}.tatum.io/v3/blockchain/token/address/SOL/{blockchain_address}
https://{region}.tatum.io/v3/blockchain/token/address/ALGO/{blockchain_address}
Solana: Get the List of NFTs per Address
For the Solana blockchain, you can now retrieve the list of NFTs that a specific blockchain address holds.
To do so, use the API for getting NFTs per address, and make sure to replace the chain path parameter with SOL.
https://{region}.tatum.io/v3/nft/address/balance/SOL/{blockchain_address}
The API returns the IDs of the NFTs connected to the address.
For a blockchain address that has fewer than 50 NFTs, the API also returns each NFT's metadata. If the metadata is not returned, you can obtain it using the metadata API.
Solana: Manage SPL Tokens
For the Solana blockchain, you can now manage SPL (Solana Program Library) tokens.
SPL tokens are Solana-specific fungible tokens equivalent to the Ethereum ERC-20 tokens.
Here is what you can do:
Deploy a smart contract for creating SPL tokens.
Use the API for deploying ERC-20 smart contracts, and make sure to choose either the ChainDeploySolanaSpl or ChainDeploySolanaSplKMS request schema.
Transfer an SPL token from one blockchain address to another one.
Use the API for transferring ERC-20 tokens, and make sure to choose either the ChainTransferSolanaSpl or ChainTransferSolanaSplKMS request schema.
Create a USDC Solana virtual account and make a deposit into this account.
Use the API for creating virtual accounts. Then, send a deposit to the account through the USDC Testnet Faucet.
Send Solana USDC/SPL token from a USDC Solana virtual account to a blockchain address.
Use the API for sending Solana assets from a virtual account to the blockchain.
Connect an SPL token to a virtual account.
Use the API for registering tokens in a virtual account, and make sure to replace the chain path parameter with SOL.