List Tokens Transfers By Address

Through this endpoint customers can obtain a list with token transfers by the address attribute. Token transfers may include information such as addresses of the sender and recipient, token name, token symbol, etc.

This refers only to transfers done for tokens not coins.

GET /blockchain-data/{blockchain}/{network}/addresses/{address}/tokens-transfers

Path Parameters

  • Required
    blockchain string

    Represents the specific blockchain protocol name, e.g. Ethereum, Ethereum Classic, etc.

    Example : ethereum
    Possible Values : ethereum
  • Required
    network 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 "ropsten", "rinkeby" are test networks.

    Example : ropsten
    Possible Values : mainnet ropsten rinkeby
  • Required
    address string

    Represents the public address, which is a compressed and shortened form of a public key.

    Example : 0x033ef6db9fbd0ee60e2931906b987fe0280471a0

Response schema

200 400 401 402 403 409 415 422 429 500
HTTP Status Code: 200
Content-Type: application/json

The request has been successful.

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2.0
  • Required
    requestId string

    Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.

    Example : 601c1710034ed6d407996b30
  • Optional
    context 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 : You can add any text here
  • Required
    data object
    • Required
      offset integer

      The starting index of the response items, i.e. where the response should start listing the returned items.

      Example : 0
    • Required
      limit integer

      Defines how many items should be returned in the response per page basis.

      Example : 50
    • Required
      total integer

      Defines the total number of items returned in the response.

      Example : 100
    • Required
      items array
      Example : Array ( )
      • Required
        contractAddress string

        Represents the contract address of the token, which controls its logic. It is not the address that holds the tokens.

        Example : 0xdac17f958d2ee523a2206206994597c13d831ec7
      • Required
        minedInBlockHeight integer

        Defines the block height in which this transaction was confirmed/mined.

        Example : 12046964
      • Required
        recipientAddress string

        Defines the address to which the recipient receives the transferred tokens.

        Example : 0xdac17f958d2ee523a2206206994597c13d831ec7
      • Required
        senderAddress string

        Defines the address from which the sender transfers tokens.

        Example : 0x65b895f400dae5541d70cbbec07527210158f6e2
      • Required
        tokenDecimals integer

        Defines the decimals of the token, i.e. the number of digits that come after the decimal coma of the token.

        Example : 6
      • Required
        tokenName string

        Defines the token's name as a string.

        Example : Tether USD
      • Required
        tokenSymbol string

        Defines the token symbol by which the token contract is known. It is usually 3-4 characters in length.

        Example : USDT
      • Required
        tokenType string

        Defines the specific token type.

        Example : ERC-20
      • Required
        tokensAmount string

        Defines the token amount of the transfer.

        Example : 9.146383
      • Required
        transactionHash 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 : 0x32de09d747bcbed41e8162681a72b2a6c760cf2116ce372fcd357c260909838a
      • Required
        transactionTimestamp integer

        Defines the specific time/date when the transaction was created in Unix Timestamp.

        Example : 1615861410
Try it out

Request Example

Content-Type: application/json
X-API-Key: my-api-key

Response Example

    "apiVersion": "2.0",
    "requestId": "601c1710034ed6d407996b30",
    "context": "You can add any text here",
    "data": {
        "offset": 0,
        "limit": 50,
        "total": 100,
        "items": [
                "contractAddress": "0xdac17f958d2ee523a2206206994597c13d831ec7",
                "minedInBlockHeight": 12046964,
                "recipientAddress": "0xdac17f958d2ee523a2206206994597c13d831ec7",
                "senderAddress": "0x65b895f400dae5541d70cbbec07527210158f6e2",
                "tokenDecimals": 6,
                "tokenName": "Tether USD",
                "tokenSymbol": "USDT",
                "tokenType": "ERC-20",
                "tokensAmount": "9.146383",
                "transactionHash": "0x32de09d747bcbed41e8162681a72b2a6c760cf2116ce372fcd357c260909838a",
                "transactionTimestamp": 1615861410