Tatum

Data API

Tatum Data API is a comprehensive solution designed for developers to easily access on-chain data such as token balances, NFT owners, and metadata, all through a suite of user-friendly APIs.

With Tatum Data API, developers can seamlessly integrate blockchain functionality into their applications, enabling them to deliver innovative, web3 solutions. This powerful indexing solution supports multiple blockchains, ensuring developers have access to the latest data across different networks.

Tatum Data API offers a reliable, scalable, and cost-effective way for developers to access on-chain data, making it an essential tool for any blockchain project.

Get tokens from a collection

10 credits per API call

Get all NFTs (ERC-721 and ERC-1155) and multitokens (ERC-1155 only) of your favorite collections! Our API lets you search for all tokens on:

  • Celo - celo / celo-testnet
  • Ethereum - ethereum / ethereum-sepolia
  • BNB (Binance) Smart Chain - bsc / bsc-testnet
  • Polygon - polygon / polygon-mumbai

To get started:

  • Provide a chain name and comma-separated list of collection addresses. Our API will return relevant information about each token, including its name, description, image, and more.
  • Aside from relevant information about each token, the response also contains metadata (they can, however, be excluded by setting excludeMetadata to true).
  • If not specified, the API returns results for all supported types of tokens (nft, multitokens), but you can also choose to filter only one tokenType.
SecurityX-API-Key
Request
query Parameters
chain
required
string (ChainEnum)

The blockchain to work with.

Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"
Example: chain=ethereum
collectionAddresses
required
string

The blockchain addresses of the collections. It is possible to enter list of up to 10 addresses as a comma separated string.

Example: collectionAddresses=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenTypes
string

The option to select only specific token types. It is possible to enter list of multiple types as a comma separated string. Use nft (includes ERC-721 and ERC-1155) or multitoken (ERC-1155 only).

Enum: "nft" "multitoken"
Example: tokenTypes=nft
excludeMetadata
boolean (ExcludeMetadata)

The option to exclude metadata from the response.

Example: excludeMetadata=true
pageSize
number (PageSize) [ 1 .. 50 ]

The number of items per page (default is 50).

Example: pageSize=10
offset
number (Offset)

The offset to obtain next page of the data.

Example: offset=1
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

Unauthorized. Not valid or inactive subscription key present in the HTTP Header.

403

Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.

500

Internal server error. There was an error on the server during the processing of the request.

get/v3/data/collections
Request samples 
Response samples 
application/json
[
  • {
    }
]
Get token metadata
5 credits per API call


Get metadata of NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) by IDs for a given token address! Our API lets you search for all tokens on:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name, token address and comma-separated list of IDs. Our API will return relevant metadata about each specified token, including its name, description, image, and more.
    • 

  • Aside from the metadata information, the response also contains token types and metadata url minted in each token.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
tokenAddress
required
string (TokenAddress) 
The blockchain address of the NFT to get metadata for.


 
 Example:  tokenAddress=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenIds
required
string
The IDs of the tokens to get metadata for.
It is possible to enter list of multiple IDs as a comma separated string.


 
 Example:  tokenIds=90,123
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/metadata
Request samples 
Response samples 
application/json
[
  • {
    }
]
Get balances of addresses
50 credits per API call


Get balances of fungible tokens (ERC-20), NFTs (ERC-721 and ERC-1155) or multitokens (ERC-1155 only) for a specific wallet address on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name and comma-separated list of addresses. Our API will return balances of each token along with further information such as its type, id, and more.
    • 

  • Aside from relevant information about each token and its balance, the response also contains metadata (they can, however, be excluded by setting excludeMetadata to true).
    • 

  • If not specified, the API returns balances for all supported types of tokens (fungible tokens, nft, multitokens), but you can also choose to filter specific tokenTypes.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
addresses
required
string
The blockchain public wallet addresses.
It is possible to enter list of up to 10 addresses as a comma separated string.


 
 Example:  addresses=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2,0xAe680Ed83baF08a8028118Bd19859F8a0E744cc6
tokenTypes
string
The option to select only specific token types.
It is possible to enter list of multiple types as a comma separated string.
Use fungible (ERC-20), nft (includes ERC-721 and ERC-1155) or multitoken (ERC-1155 only).


 Enum: "nft" "multitoken" "fungible"  
 Example:  tokenTypes=nft,multitoken
excludeMetadata
boolean (ExcludeMetadata) 
The option to exclude metadata from the response.


 
 Example:  excludeMetadata=true
pageSize
number (PageSize)   [ 1 .. 50 ] 
The number of items per page (default is 50).


 
 Example:  pageSize=10
offset
number (Offset) 
The offset to obtain next page of the data.


 
 Example:  offset=1
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/balances
Request samples 
Response samples 
application/json
{
  • "result": [
    ],
  • "prevPage": "TBD",
  • "nextPage": "TBD"
}
Get owners of a token
20 credits per API call


Get all addresses that own your favorite token (ERC-20, ERC-721 or ERC-1155)! Our API lets you search for all token owners on:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name and address of any fungible token, NFT or multitoken collection. Our API will return a list of addresses of all of their owners.
    • 

  • You can also get an owner of a specific NFT by specifying tokenId. In case of multitoken, result is an array of addresses.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
tokenAddress
required
string (TokenAddress) 
The blockchain address of the token (NFT collection or any fungible token).


 
 Example:  tokenAddress=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenId
string <uint256>  (TokenId)   <= 78 characters 
The ID of a specific NFT token.


 
 Example:  tokenId=123
pageSize
number (PageSize)   [ 1 .. 50 ] 
The number of items per page (default is 50).


 
 Example:  pageSize=10
offset
number (Offset) 
The offset to obtain next page of the data.


 
 Example:  offset=1
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/owners
Request samples 
Response samples 
application/json
[
  • "0x0bbf9f25c863fdf19e645c96280004d24f43cb38",
  • "0x0bd1b3b12db943f2310a4e53481ae97f8b6c2a75",
  • "0x281f4727081ab4a066f321fd6fc8dd0dc063e9fd",
  • "0x681cbae1c41e5eec8411dd8e009fa71f81d03f7f",
  • "0x7b49a05c15702bbe1db534058ebcc9e950c474ca"
]
Check owner of token
1 credit per API call


Check if wallet address owns any specified token (ERC-20, ERC-721 or ERC-1155) on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name, wallet address and address of any fungible token, NFT or multitoken collection. Our API will return true if provided wallet address owns them.
    • 

  • If wallet address does not own the specific token, response body is false and status code is 200.
    • 

  • It is also possible to check if wallet address owns a specific NFT by specifying a tokenId.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
address
required
string
The blockchain address of the wallet.


 
 Example:  address=0x10d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenAddress
required
string (TokenAddress) 
The blockchain address of the token (NFT collection or any fungible token).


 
 Example:  tokenAddress=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenId
string <uint256>  (TokenId)   <= 78 characters 
The ID of a specific NFT token.


 
 Example:  tokenId=123
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/owners/address
Request samples 
Response samples 
application/json
true
Get transactions
20 credits per API call


Get transactions on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name and comma-separated list of addresses. Our API will return all of their transactions along with further information such as their block number, ID of involved token, and more.
    • 

  • If not specified, the API returns transactions of various types (fungible, nft, multitoken, native, internal), but you can also choose to filter specific transactionTypes and even transactionSubtype (incoming, outgoing, zero-transfer).
    • 

  • On top of that, you can add further filters such as specifying block range where the transactions should have occurred, or address and ID of involved tokens.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
addresses
string
The blockchain public wallet addresses.
It is possible to enter list of up to 10 addresses as a comma separated string.


 
 Example:  addresses=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2,0xAe680Ed83baF08a8028118Bd19859F8a0E744cc6
transactionTypes
string
The option to filter transaction based on types.
It is possible to enter list of multiple types as a comma separated string.
Use fungible (ERC-20), nft (ERC-721 and ERC-1155), multitoken (ERC-1155), native or internal.


 Enum: "fungible" "nft" "multitoken" "native" "internal"  
 Example:  transactionTypes=fungible,nft
transactionSubtype
string
The option to filter transaction based on subtype.


 Enum: "incoming" "outgoing" "zero-transfer"  
 Example:  transactionSubtype=incoming
tokenAddress
string (TokenAddress) 
Address of a token (smart contract).


 
 Example:  tokenAddress=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenId
string <uint256>  (TokenId)   <= 78 characters 
ID of a token.


 
 Example:  tokenId=123
blockFrom
number (BlockNumber)   >= 0 
Transactions from this block onwards will be included.


 
 Example:  blockFrom=16641547
blockTo
number (BlockNumber)   >= 0 
Transactions up to this block will be included.


 
 Example:  blockTo=16641547
pageSize
number (PageSize)   [ 1 .. 50 ] 
The number of items per page (default is 50).


 
 Example:  pageSize=10
offset
number (Offset) 
The offset to obtain next page of the data.


 
 Example:  offset=1
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/transactions
Request samples 
Response samples 
application/json
{
  • "result": [
    ],
  • "prevPage": "TBD",
  • "nextPage": "TBD"
}
Get transactions by hash
5 credits per API call


Get transactions by hash on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain name and transaction hash, and our API will return a list of transactions with that hash.
    • 

  • The response will contain all the relevant information about specified transactions such as their block number, IDs of involved token, and more.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
hash
required
string
Hash of the transaction.


 
 Example:  hash=0xd49f8d6544f2822522886a02f4787a56ea93bbd636bfdf81d6795a10553d7118
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/transactions/hash
Request samples 
Response samples 
application/json
[
  • {
    },
  • {
    }
]
Get specified events
20 credits per API call


Get all events on given addresses and / or in the requested block range on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • To improve response times and obtain specific data, it is recommended to use proper filtering techniques. Please provide a chain name and a combination of filters that will accomplish this (at least block range or contract addresses must be specified).
    • 

  • It is possible to specify multiple contract addresses at once by passing them as a comma separated string.
    • 

  • If block range is not specified, the API attempts to go through all available blocks, which may result in a timeout error.
    • 

  • It is recommended to filter only one specific type of events, which comes with built-in decoding for all the supported types.
    • 

  • It is, however, also possible to filter by signature hashes, which can be passed together as a comma separated string.
    • 



As noted above, aside from general info and hashed event data, the API also decodes them for you in case you filter by one of the following supported event types:


    

  • tokenTransfer: All transfers of fungible tokens (including stablecoins) and NFTs as per ERC-20 and ERC-721 standard.
    • 

  • multitokenTransfer: All transfers of multitokens (both single transfers and batch transfers) as per ERC-1155 standard.
    • 

  • stablecoinTransfer: Refers to the transfer of specific stablecoins on the mainnet. Typically, the top 10 to 16 stablecoins on each chain according to CoinMarketCap are included. If the contractAddresses parameter is also used in the filter combination, any tokens specified in it will also be included in the list.
    • 

  • uniswapTrade: Provides all swap events that occur on both Uniswap V2 and V3. In some cases, it may not be possible to map the swapped amounts to specific tokens. As a result, certain decoded data such as token amounts might be missing or in the original big number format. This will be indicated by the response parameter partiallyRaw: true.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
contractAddresses
required
string
The blockchain addresses of the contracts where requested events were emitted.
It is possible to enter list of up to 10 addresses as a comma separated string.


 
 Example:  contractAddresses=0xd4307e0acd12cf46fd6cf93bc264f5d5d1598792
blockFrom
required
number (BlockNumber)   >= 0 
First block to start from (including this one).


 
 Example:  blockFrom=16641547
blockTo
required
number (BlockNumber)   >= 0 
Last block to finish on (including this one).


 
 Example:  blockTo=16641547
eventType
required
string
The type of events that should be returned, which comes with decoded data in the response
(cannot be used together with signatures).


 Enum: "tokenTransfer" "multitokenTransfer" "stablecoinTransfer" "uniswapTrade"  
 Example:  eventType=tokenTransfer
signatures
string
The types of events that should be returned, specified by hashed signature
(cannot be used together with eventType).
It is possible to enter list of multiple signatures as a comma separated string.


 
 Example:  signatures=0x0bcc4c97732e47d9946f229edb95f5b6323f601300e4690de719993f3c371129
pageSize
number (PageSize)   [ 1 .. 50 ] 
The number of items per page (default is 50).


 
 Example:  pageSize=10
offset
number (Offset) 
The offset to obtain next page of the data.


 
 Example:  offset=1
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/events
Request samples 
Response samples 
application/json
{
  • "chain": "ethereum-sepolia",
  • "address": "string",
  • "blockNumber": 0,
  • "timestamp": 0,
  • "decoded": {
    },
  • "raw": {
    },
  • "txHash": "string",
  • "txIndex": 0,
  • "logIndex": 0
}
Get specified blocks
10 credits per API call


Get information about blocks (when they were added, how many NFTs and events were ingested and list of transaction hashes that were processed within them) on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started, provide a chain and specify one of the filters listed below (combination of these filters is not allowed):


    

  • List of block numbers separated by comma
    • 

  • Range of block numbers
    • 

  • Date range when blocks were processed
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
blockIds
Array of integers  >= 0 
List of block numbers, separated by comma.


 
 Example:  blockIds=1,2,4,400
blockFrom
number (BlockNumber)   >= 0 
Range of block numbers. Both blockFrom and blockTo need to be specified.


 
 Example:  blockFrom=16641547
blockTo
number (BlockNumber)   >= 0 
Range of block numbers. Both blockFrom and blockTo need to be specified.


 
 Example:  blockTo=16641547
timeFrom
string
Date range when blocks were processed. Both timeFrom and timeTo need to be specified.


 
 Example:  timeFrom=2022-12-24T00:10
timeTo
string
Date range when blocks were processed. Both timeFrom and timeTo need to be specified.


 
 Example:  timeTo=2022-12-24T00:20
pageSize
number (PageSize)   [ 1 .. 50 ] 
The number of items per page (default is 50).


 
 Example:  pageSize=10
offset
number (Offset) 
The offset to obtain next page of the data.


 
 Example:  offset=1
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/blocks
Request samples 
Response samples 
application/json
[
  • {
    },
  • {
    }
]
Get latest block
1 credit per API call


Get information about latest added block on the following blockchains:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started, you can just provide a chain.


SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/blocks/latest
Request samples 
Response samples 
application/json
{
  • "blockNumber": 10,
  • "blockTimestamp": 1598671520000,
  • "hash": "0xec1a2d906f34e1981b2b1a15dbe5e10cf640e8b4b27dc056ebb65c0409b5a9af",
  • "eventIngestedSize": 0,
  • "nftIngestedSize": 0,
  • "txHashes": [
    ]
}
Get information about collection or token
1 credit per API call


Get information about your favorite token! Our API lets you search for all tokens on:


    

  • Celo - celo / celo-testnet
    • 

  • Ethereum - ethereum / ethereum-sepolia
    • 

  • BNB (Binance) Smart Chain - bsc / bsc-testnet
    • 

  • Polygon - polygon / polygon-mumbai
    • 



To get started:


    

  • Provide a chain and address of any fungible token, NFT or multitoken collection. If available, our API will return information about them such as their name, symbol, supply, and more.
    • 

  • You can also get extra infomation (such as metadata) of a specific NFT or multitoken by passing tokenId as a query parameter.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainEnum) 
The blockchain to work with.


 Enum: "ethereum" "ethereum-sepolia" "celo" "celo-testnet" "bsc" "bsc-testnet" "polygon" "polygon-mumbai"  
 Example:  chain=ethereum
tokenAddress
required
string (TokenAddress) 
The blockchain address of the token (NFT collection or any fungible token).


 
 Example:  tokenAddress=0x80d8bac9a6901698b3749fe336bbd1385c1f98f2
tokenId
string <uint256>  (TokenId)   <= 78 characters 
The ID of a specific NFT token.


 
 Example:  tokenId=123
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


404
Collection or token not found.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/tokens
Request samples 
Response samples 
application/json
{
  • "symbol": "RareItem",
  • "name": "BeefyCollectibles",
  • "supply": "13",
  • "decimals": 6,
  • "tokenType": "nft",
  • "cap": "2000000000",
  • "metadataURI": "QmYrUYv3kCXsrbs8YGguwZkyyMgGkgdQpbse8dZrDaruy5",
  • "metadata": {
    }
}
Get unspent UTXOs for an address
100 credits per API call


Get unspent UTXOs for a specific address up to a specific total amount.
If you want to prepare a transaction on UTXO-based chains like Bitcoin, you need to enter unspent UTXOs to be able to perform a transaction. By providing ```totalValue``` as a total, our API will return a list of UTXOs that will be enough to cover the transaction.

Our API lets you get the unpenst UTXOs for a specific address on:


    

  • Bitcoin - bitcoin / bitcoin-testnet
    • 

  • Litecoin - litecoin / litecoin-testnet
    • 

  • Dogecoin - doge / doge-testnet
    • 

  • Cardano - cardano / cardano-preprod
    • 



To get started:


    

  • Provide a chain and address you want to list unspent UTXOs for. If available, our API will return information about the unspent UTXOs for a specific address. API traverses latest 200k incoming transactions.
    • 



SecurityX-API-Key 
Request 
query Parameters
chain
required
string (ChainUtxoEnum) 
The blockchain to work with.


 Enum: "bitcoin" "bitcoin-testnet" "litecoin" "litecoin-testnet" "doge" "doge-testnet" "cardano" "cardano-preprod"  
 Example:  chain=bitcoin
address
required
string
The blockchain address.


 
 Example:  address=bc1qmfp2r68cde646jv5ns7x2qvah8v5qtfw8gznj2
totalValue
number  >= 0 
The total amount of transaction you want to send. Only UTXOs up to this amount will be returned, so you will not spend more than you need.


 
 Example:  totalValue=0.0001
Responses 
200
OK


400
Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.


401
Unauthorized. Not valid or inactive subscription key present in the HTTP Header.


403
Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.


500
Internal server error. There was an error on the server during the processing of the request.


get/v3/data/utxos
Request samples 
Response samples 
application/json
[
  • {
    }
]
➔ Next to Notification subscriptions