List Unconfirmed Tokens Transfers By Address
Through this endpoint customers can obtain a list with unconfirmed token transfers by the address
attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Ethereum Classic, etc.
-
Requirednetwork string
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "ropsten" are test networks.
-
Requiredaddress string
Represents the public address, which is a compressed and shortened form of a public key.
Query parameters
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user. -
Optionallimit integer
Defines how many items should be returned in the response per page basis.
-
Optionaloffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Response schema
Content-Type: application/json
The request has been successful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.Example : yourExampleString -
Requireddata object
-
Requiredlimit integer
Defines how many items should be returned in the response per page basis.
Example : 50 -
Requiredoffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Example : 0 -
Requiredtotal integer
Defines the total number of items returned in the response.
Example : 100 -
Requireditems arrayExample : Array ( )
-
RequiredcontractAddress string
Represents the contract address of the token, which controls its logic. It is not the address that holds the tokens.
Example : 0x534bD102153EF199abAe8296a2FaE4599fC44Cdc -
RequiredrecipientAddress string
Defines the address to which the recipient receives the transferred tokens.
Example : 0xc6d46aba0c6e2eb6358c4e24804158cc4d847922 -
RequiredsenderAddress string
Defines the address from which the sender transfers tokens.
Example : 0x0902a667d6a3f287835e0a4593cae4167384abc6 -
RequiredtokenDecimals integer
Defines the decimals of the token, i.e. the number of digits that come after the decimal coma of the token.
Example : 6 -
OptionaltokenId string
Represents the unique token identifier.
Example : 16721 -
RequiredtokenName string
Defines the token's name as a string.
Example : Tether USD -
RequiredtokenSymbol string
Defines the token symbol by which the token contract is known. It is usually 3-4 characters in length.
Example : USDT -
RequiredtokenType string
Defines the specific token type.
Example : ERC-20 -
OptionaltokensAmount string
Defines the token amount of the transfer.
Example : 9.146383 -
RequiredtransactionHash string
Represents the hash of the transaction, which is its unique identifier. It represents a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
Example : 0xbc8245ba5cccb524d91256224689ac0f16678321a266bab8197ad7daab4c9e16 -
RequiredtransactionTimestamp integer
Defines the specific time/date when the transaction was created in Unix Timestamp.
Example : 1615861410
-
-