What's New
Dashboard 1.26
Reorganized left-pane menu

- The Debug, Deposits, Subscriptions, Webhooks, and Virtual Accounts options, which were previously hidden under Explore, are now available directly from the menu. Just to remind you what these options do:
- Debug lists the last 100 API calls that you made.
- Deposits lists the deposits that you have made and received and lets you filter them by different criteria.
- Subscriptions lists your existing subscriptions and allows you to create a new subscription and delete an existing subscription right from the Dashboard.
- Webhooks lists the last 10 webhook calls that have been made based on your subscriptions.
- Virtual Accounts lists your existing virtual accounts and lets you filter them by different criteria.
- A few options that were rarely used were removed. This allows you to focus only on those things that really matter.
- The NFT Minter option remains in the menu, and its functionality has not changed - you can still mint NFTs right from the Dashboard and without the need to make API calls.
A new look-and-feel of the API Keys section
We updated and reorganized the API Keys section to give you a better overview of your API keys (paid and free), your plans, and the number of credits available and used. This information now appears right on the top of the screen:

Right under this information, we added links to various useful resources: our video tutorials, user documentation, API Reference, and blog. They are displayed to the users who have recently joined to help them navigate Tatum faster.
Dashboard 1.25
- 1.In the left panel, click Explore, then click Subscriptions.
- 2.Click Delete for the subscription that you want to delete.

Deleting a subscription from the Dashboard is the same as deleting it using the API for canceling a subscription and consumes 1 credit from your credit allowance.
JavaScript SDK and Key Management System (KMS)
On December 12, 2022, a third-party dependency for Ethereum and Celo in our JavaScript SDK v1 and KMS will stop providing reliable data about the gas price.
This has a critical impact on any scenario where the transaction fee is not explicitly set in a transaction and gets calculated automatically, specifically:
- When you are using an SDK function that has the
gasPrice
andgasLimit
parameters (either nested under the optionalfee
parameter or as two separate optional parameters) and you do not set these parameters in your calls - When you are using KMS to sign your transactions (KMS calls the same functions internally in the background when processing the transactions to be signed)
An example of the impacted JavaScript SDK v1 functions is
prepareEthOrErc20SignedTransaction
for transferring ETH or Ethereum fungible tokens from one blockchain address to another; here is the description of the underlying API in the API Reference:
To address this issue, we have prepared updates to JavaScript SDK v1 and KMS.
How do you know whether you are affected?
- You are not affected if you call the APIs directly or use the C# SDK. We have already updated the APIs and the underlying infrastructure on our side, and you do not have to take any action. All the necessary changes are available for you automatically.
- You are affected if you use JavaScript SDK v1 and/or KMS. Please take the required actions.
ACTION REQUIRED!
If you are using JavaScript SDK v1 and/or KMS, upgrade them to the latest versions:
Do so as soon as possible or by December 12, 2022, the latest.
What will happen if you do not upgrade the JavaScript SDK and/or KMS?
After December 12, 2022, all SDK calls without the gas price explicitly set will most probably fail. The transaction fee will be calculated as too high or too low, which will lead to wasting assets or too long processing of the transactions.
In KMS, the signing process may start failing, and the transactions will not be properly signed and broadcasted to the blockchain.
Temporary workaround for JavaScript SDK v1
If for any reason you cannot upgrade your JavaScript SDK v1 by December 12, 2022, set the fee manually for any Ethereum and Celo transactions by setting the
gasPrice
and gasLimit
parameters, either nested under the optional fee
parameter or as two separate parameters.However, we strongly recommend that you upgrade your JavaScript SDK v1 to the latest version as soon as possible.
TIP: Use a new API for getting the gas price
A new API for getting the recommended gas price on Ethereum, Bitcoin, Litecoin, and Dogecoin is available for use. For more information, please visit our API Reference.
API v3.17.1
We have added a few more blockchains to the list of the blockchains to which you can connect directly via the node provided by Tatum:
- BNB Beacon Chain
https://api.tatum.io/v3/blockchain/node/
BNB
/{your_api_key}/{rpc_path}
- Flow
https://api.tatum.io/v3/blockchain/node/
FLOW
/{your_api_key}/{rpc_path}
- XRP
https://api.tatum.io/v3/blockchain/node/
XRP
/{your_api_key}/{rpc_path}
- Zilliqa
https://api.tatum.io/v3/blockchain/node/
ZIL
/{your_api_key}/{rpc_path}
You can now mint fractional NFTs on Algorand.
A fractional NFT is an NFT that has been divided into multiple equal shares (fractions). For more information, please refer to the Algorand user documentation.
To mint a fractional NFT, use one of the Algorand schemas of the minting API (
MintNftAlgorand
, MintNftAlgorandKMS
, or MintNftExpressAlgorand
) and set the total
and decimals
parameters to specify the number of fractions in the NFT and the number of decimal places in a fraction, respectively:{
"chain": "ALGO",
"url": "https://my_token_data.com",
"name": "My fractional NFT",
...
"attr": {
...
"total": "10"
,
"decimals": "1"
,
...
}
When eventually transferring a fractional NFT, use the appropriate Algorand schema of the transferring API (
TransferNftAlgo
, TransferNftAlgoKMS
, or TransferNftAlgoExpress
) and set the amount
parameter to specify the number of the NFT fractions to transfer:{
"chain": "ALGO",
"to": "TMETT6BXL3QUH7AH5TS6IONU7LVTLKIGG54CFCNPMQXWGRIZFIESZBYWP4",
...
"amount": "1"
}
For more information about minting NFTs on Algorand using NFT Express, please refer to our user documentation.
This feature is in alpha.
You can now build an NFT marketplace on Solana.
To do so, use the
GenerateMarketplaceSolana
and GenerateMarketplaceSolanaKMS
schemas of the API for creating an NFT marketplace.Then, you can use the existing APIs to perform any standard action related to an NFT marketplace such as selling and buying assets or getting information about a listing, and so on - just make sure to use the Solana-specific schema or to specify
SOL
in the URL path.We also introduced new marketplace-related APIs for Solana specifically:
For more information about NFT marketplaces, please refer to our user documentation and the API Reference.
To make Tatum integration smoother and easier, we introduced a new server domain name for the Tatum API:
https://api.tatum.io
You no longer need to specify a region identifier (
eu1
or us-west1
) in the domain name. https://api.tatum.io
covers it all.The previously used domain names that include region identifiers are still valid!
Any API calls made to the old domain names are automatically redirected to the new domain name.
https://
api-eu1
.tatum.io/{path}
→ https://
api
.tatum.io/{path}
https://
api-us-west1
.tatum.io/{path}
→ https://
api
.tatum.io/{path}
You do not need to make any changes in your current implementations of the Tatum APIs. However, if you are building a brand new implementation, please use the new server domain name:
https://api.tatum.io
C# SDK v2.0
We have released v2.0 of the Tatum C# SDK.
The C# SDK v2.0 allows you as a C# developer to interact with the Tatum APIs and build applications around them.
What blockchains are supported?
The C# SDK v2.0 supports Ethereum and Bitcoin for now, but we are working on adding support for more blockchains, so stay tuned!
What does v2.0 offer?
- Integration with the Tatum APIs for Ethereum and Bitcoin
- Modularity with separate blockchain-targeted packages
- Built-in model validation
- Local cryptographic functionalities using relevant packages such as Nethereum and NBitcoin
- A demo application and code examples demonstrating how to use the SDK in different scenarios
- Injectable
HttpClient
and the option to use the Tatum Client as aTyped Client
in .NET applications - An interface for calls returning the response model or throwing an exception
- An interface for calls returning an
ApiResponse
wrapper - Support for
CancellationToken
- Built-in documentation generated from OpenAPI specification files
What to do if you are using v1.0
The C# SDK v1.0 has not been maintained by Tatum for a while now and is ultimately community-driven. If you are using the Tatum C# SDK, we recommend that you switch to v2.0.
The SDK v2.0 is structurally different from v1.0, therefore there is no option to upgrade from v1.0 to v2.0. You have to start from scratch. However, we do recommend that you move to v2.0 because v1.0 does not receive new features or bug fixes and no technical support is provided.
Need help?
- If you are having a technical issue with the C# SDK, please submit an issue to the C# SDK GitHub repository.
- If you have a question about the C# SDK in general, please post a question in the
#tatum-c-sharp
Discord channel.
API v3.17
We have added two more blockchains to the list of the blockchains to which you can connect directly via the node provided by Tatum:
New options are available for you when you are transferring cryptocurrency on Bitcoin, Bitcoin Cash, or Litecoin.
Applicable to Bitcoin, Bitcoin Cash, and Litecoin
You can now explicitly specify the amount of the fee that you want to pay for a transfer transaction and the address where the change (any extra funds remaining after the transaction has been completed) will be sent.
{
"fromAddress": [
{
"address": "2N9bBiH2qrTDrPCzrNhaFGdkNKS86PJAAAS",
"privateKey": "cVX7Y...pzobf"
}
],
"to": [
{
"address": "2MzNGwuKvMEvKMQogtgzSqJcH2UW3Tc5oc7",
"value": 0.02969944
}
],
"fee": 0.00005
,
"changeAddress": "2TDrPCzrNhaFS86PJAAASGN9bBiH2qrdkNK"
}
For more information, refer to the API Reference on transferring cryptocurrency on Bitcoin, Bitcoin Cash and Litecoin.
The options of specifying the transaction fee amount and change address have been already available for Dogecoin.
Applicable only to Bitcoin and Litecoin
If you use Key Management System (KMS) and send cryptocurrency from blockchain addresses (as opposed to sending it from UTXOs), you can now sign transactions with a mnemonic-based signature ID. In this case, you need to also provide the index of the address that you are using this signature ID for.
{
"fromAddress": [
{
"address": "2N9bBiH2qrTDrPCzrNhaFGdkNKS86PJAAAS",
"signatureId": "1f7f7c0c-...-4b67c43918f6", // mnemonic-based
"index": 459
}
],
"to": [
{
"address": "2MzNGwuKvMEvKMQogtgzSqJcH2UW3Tc5oc7",
"value": 0.02969944
}
]
}
A new option is available for you when you are transferring cryptoassets on Solana. We also enhanced notifications fired by
ADDRESS_TRANSACTION
subscriptions.When you are transferring SPL tokens or SOL, you can now specify a different address to cover the gas fees instead of the address that the tokens or SOL are transferred from. To do that, specify the
feePayer
and feePayerPrivateKey
/feePayerSignatureId
parameters in the API request body.- Transferring SPL tokens (see the
chainTransferSolanaSpl
andchainTransferSolanaSplKMS
schemas of the request body){ "chain": "SOL", "from": "BL4Xgn1jkuU4Yr3SQ4HG8cD5SBrsSk7BihKzkb5zTUfs", "to": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", "contractAddress": "DgS3XZzWiFgrVXfWoPJFykfMwA9WNShzPJbbb9DNXsfg", "amount": "100000", "digits": 18, "fromPrivateKey": "Hdz3ij...buk9V",
"feePayer": "SQ4HG8cD5SBrsSk7B3ihKzkb5zTUfsBL4Xgn1jkuU4Yr"
,
"feePayerPrivateKey": "YdQ1i...DMsGaf"
}
- Transferring SOL
{ "from": "BL4Xgn1jkuU4Yr3SQ4HG8cD5SBrsSk7BihKzkb5zTUfs", "to": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ", "amount": "100000", "fromPrivateKey": "Hdz3ij...buk9V",
"feePayer": "SQ4HG8cD5SBrsSk7B3ihKzkb5zTUfsBL4Xgn1jkuU4Yr"
,
"feePayerPrivateKey": "YdQ1i...DMsGaf"
}
We added a new parameter,
addressesRiskRatio
, to the notifications fired by ADDRESS_TRANSACTION
subscriptions. This parameter provides information about risk levels assigned to the addresses with which your address communicated within the transaction. The addresses are assessed using the AML/CFT solution by BlockmateBC.{
"address": "BL4Xgn1jkuU4Yr3SQ4HG8cD5SBrsSk7BihKzkb5zTUfs",
"txId": "2rdy3...DBk7A",
"asset": "3gUeeR3BfVhukYJMwtHownRtRkGcf1bvwiV8TbKMZBVz",
...
"addressesRiskRatio": [
{
"vTEfAhXTmvgFmepgfhzBbRrJ4EtUP9adbMJjpzLsDMk": 0
},
{
"zBbRrJ4EtUP9adbMJjpzLsDMkvTEfAhXTmvgFmepgfh": 100
}
]
}
This parameter is enabled only in the notifications sent from the Solana mainnet. This parameter may not appear in a notification if the risk assessment information is not available or could not be retrieved.
KMS v6.2
We released version 6.2 of our Key Management System (KMS), which is a comprehensive security solution that generates and stores private keys and uses them to sign transactions locally.
For Bitcoin and Litecoin, KMS can now support mnemonic-based signature IDs.
To download or upgrade KMS, please visit our GitHub page. To learn how to use KMS, see Tatum Key Management System (KMS).
API v3.16
In addition to Sepolia, we now support Goerli on Ethereum.
Goerli is an Ethereum proof-of-authority testnet that works across clients. For more information about Goerli, please see the Ethereum user documentation about the Ethereum testnets.
Currently, you can use Goerli in the following scenarios:
- If you work with Ethereum via a Tatum node. Just add the
testnetType
parameter to the API endpoint URL and set it toethereum-goerli
:https://{region}.tatum.io/v3/blockchain/node/
ETH
/{your_api_key}/{rpc_path}?
testnetType=ethereum-goerli
ADDRESS_TRANSACTION
CONTRACT_NFT_TXS_PER_BLOCK
CONTRACT_MULTITOKEN_TXS_PER_BLOCK
CONTRACT_LOG_EVENT
Similar to the previous point, add thetestnetType
parameter to the API endpoint URL and set it toethereum-goerli
:https://{region}.tatum.io/v3/subscription?
testnetType=ethereum-goerli
We are working on implementing Goerli in all our APIs that support Ethereum. Stay tuned!
What is Gas Pump?
Gas Pump is Tatum's feature that helps you manage gas fees in a custodial application. When you use Gas Pump, gas fees for any transaction made by your customers (users of your custodial application) are automatically deducted from the master address instead of the customer's address. This eliminates the need to send crypto to each customer's address to pay for gas fees.
What has changed and what remained unchanged?
The main changes were made in the processes of setting up a Gas Pump solution:
- You no longer need to deploy a separate smart contract that would act as a gas pump wallet to cover your customers’ gas fees. Instead, you would start with precalculating gas pump addresses that you can immediately assign to the customers of your custodial application, and the customers can start receiving funds to their addresses right away. No gas fee is applied to the precalculation operation.
- Gas fees are first introduced when your customers decide to send funds from their gas pump addresses to other blockchain addresses. To allow them to do that, you need to activate the addresses. The activation operation costs some amount of gas on a blockchain, so you would activate only those addresses that will be sending funds instead of activating all the addresses.
What has not changed are the processes for sending one or multiple assets from a gas pump address as well as approving the asset transfer. They work exactly as they worked before.
What’s the new workflow to set up Gas Pump?
Here is how it works now:
- 1.
- 2.Set up the activation process to activate a gas pump address by demand (for example, you may want to activate an address when the customer tries to send an asset from this address for the first time).
- 3.Any time a customer tries to send funds from their gas pump address, check whether the address is activated before allowing the customer to complete the transfer.
What about the APIs?
To help you understand the changes better, here is how the API Reference was updated to reflect the new workflow:

- #1 are the newly added APIs.
- #2 are the APIs that remain unchanged and work exactly as before.
- #3 are the APIs calls that were replaced by the new APIs and are now deprecated.
How does this affect the Gas Pump solution running in your application?
The Gas Pump solution that you implemented in your application will continue working normally. The changes that we introduced do not break any existing implementation, and you do not need to make any immediate change to your current processes.
Here is what you need to know:
- If you need to add more gas pump addresses, you can still use the deprecated API for generating the addresses.
- If you added new addresses by using the deprecated API for generating the addresses, you still can use the deprecated API for getting gas pump addresses from the transaction.
However, we recommend that you switch to the new workflow: next time you need to add new addresses, precalculate them!
Where can you find more information?
Please refer to Pay Gas Fees with Tatum Gas Pump and the API Reference.
When working with blockchains by connecting to a blockchain node using the
POST
or PUT
method, you can now submit multiple RPC methods in one API call for the blockchains using the JSON-RPC 2.0 specification.To do so, construct the request body as follows:
[
{
"jsonrpc": "2.0",
"id": 1,
"method": "{method_1_name}",
"params": []
},
{
"jsonrpc": "2.0",
"id": 2,
"method": "{method_2_name}",
"params": []
},
...
]
Please be aware that the number of credits consumed by one API call depends on how many methods you submitted in the call:
- Connecting using
POST
:- 50 credits per
debug
*/trace
* method (for EVM-based blockchains) - 5 credits per
eth_call
method (for EVM-based blockchains) - 2 credits per any other RPC method
- Connecting using
PUT
: 2 credits per RPC method
For a few types of the notification subscriptions, the number of credits that each notification consumes was updated.
Here are the notification types that were affected and how many credits they consume now:
ADDRESS_TRANSACTION
- Bitcoin (BTC) - 5 credits per address per day
- Bitcoin Cash (BCH) - 5 credits per address per day
- Dogecoin (DOGE) - 7 credits per address per day
- Litecoin (LTC) - 7 credits per address per day
CONTRACT_NFT_TXS_PER_BLOCK
- 500,000 credits per day on any supported blockchainCONTRACT_MULTITOKEN_TXS_PER_BLOCK
- 500,000 credits per day on any supported blockchainCONTRACT_LOG_EVENT
- 50,000 credits per day on any supported blockchain
Following the deprecation, we disabled and completely removed Qtum from our platform. It is no longer supported.
KMS v5.1
We released version 5.1 of our Key Management System (KMS), which is a comprehensive security solution that generates and stores private keys and uses them to sign transactions locally.
To download or upgrade KMS, please visit our GitHub page. To learn how to use KMS, see Tatum Key Management System (KMS).
API v3.15.0
We have enabled quite a few new blockchains in the API for connecting to a blockchain via a Tatum node:
https://{region}.tatum.io/v3/blockchain/node/
{blockchain}
/{your_api_key}/{rpc_path}
Now, you can you this API to connect to the following blockchains:
- Arbitrum (ARB)
- Aurora (AURORA)
- Cronos (CRO)
- Gnosis (GNO)
- Kusama (KSM)
- NEAR (NEAR)
- Oasis (OASIS)
- Optimism (OPTIMISM)
- Palm (PALM)
- Polkadot (DOT)
- RSK (RSK)
- Tezos (TEZOS)
- TRON (TRON)
For more information about the API for connecting to a blockchain via a Tatum node, please refer to the API Reference.
On Solana, you can now mint an NFT as part of a collection. You can also verify that an NFT is indeed a part of a collection.
- The collection must be a sized collection that was introduced in Version 1.3 of the Metaplex Token Metadata program.
- Verifying an NFT means that the NFT is really a part of the collection (setting the
Verified
parameter totrue
for the NFT)
To know more about Solana collections and verification, please refer to the Solana user documentation.
Minting NFTs in a collection
Minting an NFT as part of a collection is supported for both minting via NFT Express and minting natively. In either case, you have to add the
collection
parameter to the metadata
section of the API request body and set it to the blockchain address of the NFT collection where the NFT should be minted in:{
"chain": "SOL",
"to": "FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ",
...
"metadata": {
"name": "My NFT",
"symbol": "NFT_SOL_CLASSIC",
"sellerFeeBasisPoints": 0,
"uri": "https://my_nft_data.com",
"collection": "66MZJWWM7ucWay8R2BzYgZnSu6zbMBVKBQz1if85d7ud"
}
}
Verifying the NFT in the collection
- If you mint the NFT natively, the minted NFT gets automatically verified in the collection at the time of the minting, and you do not need to perform any additional steps to verify it. The verification will be done on behalf of the blockchain address specified in the
from
parameter in the API request body. - If you mint the NFT using NFT Express, the NFT is minted as not verified. To verify the NFT in the collection, use the verification API.
{ "chain": "SOL", "nftAddress": "CHw1Fy5YdbaaosLXrrxhuc3X3fpssMqDQm9XwJh9LPGe", "collectionAddress": "66MZJWWM7ucWay8R2BzYgZnSu6zbMBVKBQz1if85d7ud", "from": "XsfgDgS3XZzWiFgrVXfWoPJFykfMwA9WNShzPJbbb9DN", "fromPrivateKey": "3abc79...391ad" }
Need more information?
Please refer to our API Reference:
We added three new types of the subscriptions that allow you to get notified about various events related to smart contracts across a whole blockchain:
CONTRACT_LOG_EVENT
CONTRACT_NFT_TXS_PER_BLOCK
CONTRACT_MULTITOKEN_TXS_PER_BLOCK
What do these new notification types do?
- A subscription of the
CONTRACT_LOG_EVENT
type sends a notification about any event that was emitted from any smart contract on a blockchain. - A subscription of the
CONTRACT_NFT_TXS_PER_BLOCK
type sends a notification about any event of minting, transferring, or burning an NFT that was emitted from any smart contract on a blockchain. - A subscription of the
CONTRACT_MULTITOKEN_TXS_PER_BLOCK
type sends a notification about any event of minting, transferring, or burning a Multi Token that was emitted from any smart contract on a blockchain.
These notifications are fired as a batch notification per block: a notification includes all the relevant events from all smart contracts that got recorded into a block, so you get one notification per block, not per individual event.
What blockchains are supported?
The new subscription types are supported on the following blockchains:
- BNB Smart Chain
- Celo
- Ethereum
- Klaytn
- Polygon
Need more information?
For information about the new notification types, their body structure, and credits consumed, please refer to the API for creating subscriptions in our API Reference.
We deprecated support for Cardano.
What does it mean?
- The blockchain-specific APIs such as
https://{region}.tatum.io/v3/
ada
/...
are now marked as deprecated in the API Reference. While those APIs may still be usable, they would accept calls only to the mainnet. Calls to the testnet are not supported. We recommend that you stop using these APIs. - In the APIs where Cardano or its assets can be used as a parameter in the request body or as a path parameter, Cardano or ADA are no longer available in the list of available values for these parameters. For example, ADA is no longer listed as a possible value for the currency parameter for
https://{region}.tatum.io/v3/tatum/rate/{currency}
. Other than that, those APIs do not change in any way.
Need help?
If you have any question or concern regarding the deprecation, please contact Tatum Support at [email protected] or post a question in the
#api
channel on our Discord.Error messages with a server code of
4xx
and 5xx
may now contain the cause
parameter in the response body with additional information about the cause of the error and other details that may help fix the issue.For example:
{
"statusCode": 403,
"errorCode": "sol.transaction.failed",
"message": "Failed creating transaction. ",
"cause": "unknown signer: FykfMwA9WNShzPJbbb9DNXsfgDgS3XZzWiFgrVXfWoPJ"
}
If no additional information is available for the error, the
cause
parameter is not returned.Please be aware that the number of sent notifications (web hooks) for the Free pricing plan is limited to 1,000 per month. The notifications above the limit of 1,000 are not sent.
Following the deprecation, we disabled and completely removed Terra from our platform. It is no longer supported.
Dashboard v1.24.0
Click your avatar in the top right corner, and select Billing.

Your credit consumption history is available under Your credit consumption.

The number of credits consumed is broken down by billing period (one period per page). The credits spent during one billing period are grouped by the pricing plan and the API keys.
Need more information?
API v3.14.0
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 totrue
, 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 theblockNumber
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 themempool
parameter, but it will include the number of the block where the transaction was recorded into. NOTE: Nothing has changed forADDRESS_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, theblockHash
andblockHeight
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 theACCOUNT_INCOMING_BLOCKCHAIN_TRANSACTION
type. NOTE: Nothing has changed forACCOUNT_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?
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?
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}
KMS v5.0
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
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.
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.
API v3.12.0
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
/...
orhttps://{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 forhttps://{region}.tatum.io/v3/tatum/rate/{currency}
. Other than that, those APIs do not change in any way. - For EOSIO and Lisk, 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
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!
Dashboard v1.22.0
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.
API v3.11.0
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}
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.
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
orChainDeploySolanaSplKMS
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
orChainTransferSolanaSplKMS
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 withSOL
.
Last modified 8mo ago