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.ADDRESS_TRANSACTION
type sends a notification about any transaction (incoming or outgoing) at a specified blockchain address.ACCOUNT_PENDING_BLOCKCHAIN_TRANSACTION
type sends a notification about incoming transactions on a virtual account.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.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.https://{region}.tatum.io/v3/blockchain/node/
FTM
/{your_api_key}/{rpc_path}
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
native
in the notifications."amount": "-2"
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.currency
parameter for https://{region}.tatum.io/v3/tatum/rate/{currency}
.
Other than that, those APIs do not change in any way.#api
channel on our Discord.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}
chain
path parameter with SOL
.https://{region}.tatum.io/v3/nft/address/balance/
SOL
/{blockchain_address}
ChainDeploySolanaSpl
or ChainDeploySolanaSplKMS
request schema.ChainTransferSolanaSpl
or ChainTransferSolanaSplKMS
request schema.chain
path parameter with SOL
.