Module cryptoapis::apis::unified_endpoints_api
source · [−]Enums
struct for typed errors of method estimate_transaction_smart_fee
struct for typed errors of method get_address_balance
struct for typed errors of method get_address_details
struct for typed errors of method get_block_details_by_block_hash
struct for typed errors of method get_block_details_by_block_height
struct for typed errors of method get_fee_recommendations
struct for typed errors of method get_last_mined_block
struct for typed errors of method get_next_available_nonce
struct for typed errors of method get_raw_transaction_data
struct for typed errors of method get_transaction_details_by_transaction_id
struct for typed errors of method list_confirmed_tokens_transfers_by_address_and_time_range
struct for typed errors of method list_confirmed_transactions_by_address_and_time_range
struct for typed errors of method list_confirmed_transactions_by_address
struct for typed errors of method list_internal_transactions_by_address_and_time_range
struct for typed errors of method list_latest_mined_blocks
struct for typed errors of method list_transactions_by_block_hash
struct for typed errors of method list_transactions_by_block_height
struct for typed errors of method list_unconfirmed_transactions_by_address
struct for typed errors of method list_unspent_transaction_outputs_by_address
Functions
Through this endpoint, customers can estimate the approximate fee per kilobyte needed for a transaction to begin confirmation within the confirmationTarget blocks when possible. After which it will return the number of blocks for which the estimate is valid.
Through this endpoint the customer can receive the balance of 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.
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.
Through this endpoint customers can obtain basic information about a given mined block, specifically by using the hash parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can obtain basic information about a given mined block, specifically by using the height parameter. These block details could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can obtain fee recommendations. Our fees recommendations are based on Mempool data which makes them much more accurate than fees based on already mined blocks. Calculations are done in real time live. Using this endpoint customers can get gas price for Ethereum, fee per byte for Bitcoin, etc.
Through this endpoint customers can fetch the last mined block in a specific blockchain network, along with its details. These could include the hash of the specific, the previous and the next block, its transactions count, its height, etc. Blockchain specific data is information such as version, nonce, size, bits, merkleroot, etc.
Through this endpoint customers can get information about the next available nonce by providing the specific blockchain, network and address.
Through this endpoint customers can get information on a transaction in its raw format by providing its transactionId.
Through this endpoint customers can obtain details about a transaction by the transaction’s unique identifier. In UTXO-based protocols like BTC there are attributes such as transactionId and transaction hash. They still could be different. In protocols like Ethereum there is only one unique value and it’s hash.
Through this endpoint customers can obtain a list with confirmed token transfers by the address attribute and the query parameters fromTimestamp and toTimestamp which gives customers the opportunity to filter the results by a specified time period. {note}This refers only to transfers done for confirmed tokens not coins.{/note}
This endpoint will list transactions by an attribute address. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.
This endpoint will list confirmed transactions by the attribute address and the query parameters fromTimestamp and toTimestamp which gives customers the opportunity to filter the results by a specified time period.
Through this endpoint customers can list internal transactions by the address attribute and the query parameters fromTimestamp and toTimestamp which gives customers the opportunity to filter the results by a specified time period.
Through this endpoint customers can list up to 50 from the latest blocks that were mined.
This endpoint will list transactions by an attribute transactionHash. The transactions listed will detail additional information such as addresses, height, time of creation in Unix timestamp, etc.
This endpoint will list transactions by an attribute blockHeight. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.
Through this endpoint customers can list transactions by address that are unconfirmed.
Through this endpoint customers can list their transactions’ unspent outputs by address.