Get Address Details
Through this endpoint the customer can receive basic information about a given address based on confirmed/synced blocks only. In the case where there are any incoming or outgoing unconfirmed transactions for the specific address, they will not be counted or calculated here. Applies only for coins.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, 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.
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
-
Requireditem object
-
RequiredtransactionsCount 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 : 3 -
RequiredconfirmedBalance object
-
Requiredamount string
Object representation of the total balance of the address
-
Requiredunit string
Represents the unit of the confirmed balance.
Example : BTC
-
-
RequiredtotalReceived object
-
Requiredamount string
Defines the total amount of all coins received to the address, based on confirmed transactions.
Example : 5.6 -
Requiredunit string
Represents the unit of the total received amount.
Example : BTC
-
-
RequiredtotalSpent object
-
Requiredamount string
Defines the total amount of all spent by this address coins, based on confirmed transactions.
Example : 2.1 -
Requiredunit string
Represents the unit of the total spent amount.
Example : BTC
-
-
RequiredincomingTransactionsCount integer
Numeric representation of the received transaction count of the address
Example : 2 -
RequiredoutgoingTransactionsCount integer
Numeric representation of the sent transaction count of the address
Example : 2
-
-