Get Address Details From Callback

This endpoint creates a shortcut to obtain information from Blockchain data by going through Blockchain Events and a specific Event Subscription. It provides data for a specific address from the Event it takes part in only if the address already exists in the blockchain events subscriptions. It applies only for Events related to that customer.

Single Result - This endpoint returns only one single result. GET /blockchain-events/{blockchain}/{network}/addresses/{address}

Path Parameters

  • Required
    blockchain string

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

    Example : bitcoin
    Possible Values : bitcoin bitcoin-cash litecoin dash dogecoin ethereum ethereum-classic binance-smart-chain xrp zilliqa zcash
  • 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 "testnet", "ropsten" are test networks.

    Example : testnet
    Possible Values : mainnet testnet ropsten mordor
  • Required
    address string

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

    Example : mzYijhgmzZrmuB7wBDazRKirnChKyow4M3

Query parameters

  • 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 : yourExampleString

Response schema

200 400 401 402 403 404 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 : 2021-03-20
  • 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 : yourExampleString
  • Required
    data object
    • Required
      item object
      • Required
        incomingTransactionsCount integer

        Defines the count of the incoming transactions.

        Example : 3
      • Required
        outgoingTransactionsCount integer

        Defines the count of the outgoing transactions.

        Example : 2
      • Required
        transactionsCount integer

        Represents the total number of confirmed coins transactions for this address, both incoming and outgoing. Applies for coins only and not tokens transfers e.g. for Ethereum. transactionsCount could result as less than incoming and outgoing transactions put together (e.g. in Bitcoin), due to the fact that one and the same address could be in senders and receivers addresses.

        Example : 2
      • Required
        confirmedBalance object
        • Required
          amount string

          Defines the total balance of the address that is confirmed. It doesn't include unconfirmed transactions.

          Example : 3.5
        • Required
          unit string

          Represents the unit of the confirmed balance.

          Example : BTC
      • Optional
        totalReceived object
        • Optional
          amount string

          Defines the total amount of all coins received to the address, based on confirmed transactions.

          Example : 5.6
        • Optional
          unit string

          Represents the unit of the total received amount.

          Example : BTC
      • Optional
        totalSpent object
        • Optional
          amount string

          Defines the total amount of all spent by this address coins, based on confirmed transactions.

          Example : 2.1
        • Optional
          unit string

          Represents the unit of the total spent amount.

          Example : BTC
      • Optional
        sequence integer

        Defines the transaction input's sequence as an integer, which is is used when transactions are replaced with newer versions before LockTime.

        Example : 25648975

Credits Cost : 5 Credits For 1 Result(s)

Try it out

Request Example

GET
https://rest.cryptoapis.io/blockchain-events/bitcoin/testnet/addresses/mzYijhgmzZrmuB7wBDazRKirnChKyow4M3?context=yourExampleString
Headers
Content-Type: application/json
X-API-Key: my-api-key

Response Example

{
    "apiVersion": "2021-03-20",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "item": {
            "incomingTransactionsCount": 3,
            "outgoingTransactionsCount": 2,
            "transactionsCount": 2,
            "confirmedBalance": {
                "amount": "3.5",
                "unit": "BTC"
            },
            "totalReceived": {
                "amount": "5.6",
                "unit": "BTC"
            },
            "totalSpent": {
                "amount": "2.1",
                "unit": "BTC"
            },
            "sequence": 25648975
        }
    }
}