# \InformativeApi All URIs are relative to *https://rest.cryptoapis.io* Method | HTTP request | Description ------------- | ------------- | ------------- [**get_transaction_request_details**](InformativeApi.md#get_transaction_request_details) | **GET** /wallet-as-a-service/transactionRequests/{transactionRequestId} | Get Transaction Request Details [**get_wallet_asset_details**](InformativeApi.md#get_wallet_asset_details) | **GET** /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network} | Get Wallet Asset Details [**get_wallet_transaction_details_by_transaction_id**](InformativeApi.md#get_wallet_transaction_details_by_transaction_id) | **GET** /wallet-as-a-service/wallets/{blockchain}/{network}/transactions/{transactionId} | Get Wallet Transaction Details By Transaction ID [**list_all_assets_by_wallet_id**](InformativeApi.md#list_all_assets_by_wallet_id) | **GET** /wallet-as-a-service/wallets/{walletId}/assets | List All Assets By Wallet ID [**list_all_assets_from_all_wallets**](InformativeApi.md#list_all_assets_from_all_wallets) | **GET** /wallet-as-a-service/wallets/all-assets | List All Assets From All Wallets [**list_deposit_addresses**](InformativeApi.md#list_deposit_addresses) | **GET** /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses | List Deposit Addresses [**list_supported_tokens**](InformativeApi.md#list_supported_tokens) | **GET** /wallet-as-a-service/info/{blockchain}/{network}/supported-tokens | List Supported Tokens [**list_wallet_transactions**](InformativeApi.md#list_wallet_transactions) | **GET** /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/transactions | List Wallet Transactions ## get_transaction_request_details > crate::models::GetTransactionRequestDetailsR get_transaction_request_details(transaction_request_id, context) Get Transaction Request Details Through this endpoint customers can obtain details on transaction request. {note}This regards **transaction requests**, which is not to be confused with **transactions**. Transaction requests may not be approved due to any reason, hence a transaction may not occur.{/note} ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **transaction_request_id** | **String** | Represents the unique ID of the transaction request. | [required] | **context** | Option<**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. | | ### Return type [**crate::models::GetTransactionRequestDetailsR**](GetTransactionRequestDetailsR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## get_wallet_asset_details > crate::models::GetWalletAssetDetailsR get_wallet_asset_details(blockchain, network, wallet_id, context) Get Wallet Asset Details Through this endpoint customers can obtain details on all assets (coins, fungible tokens, non-fungible tokens) for the entire Wallet. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [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. | [required] | **wallet_id** | **String** | Defines the unique ID of the Wallet. | [required] | **context** | Option<**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. | | ### Return type [**crate::models::GetWalletAssetDetailsR**](GetWalletAssetDetailsR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## get_wallet_transaction_details_by_transaction_id > crate::models::GetWalletTransactionDetailsByTransactionIdr get_wallet_transaction_details_by_transaction_id(blockchain, network, transaction_id, context) Get Wallet Transaction Details By Transaction ID Through this endpoint users can obtain Wallet transaction information by providing a `transactionId`. Customers can receive information only for a transaction that has been made from their own wallet. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [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. | [required] | **transaction_id** | **String** | Represents the unique identifier of a transaction, i.e. it could be `transactionId` in UTXO-based protocols like Bitcoin, and transaction `hash` in Ethereum blockchain. | [required] | **context** | Option<**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. | | ### Return type [**crate::models::GetWalletTransactionDetailsByTransactionIdr**](GetWalletTransactionDetailsByTransactionIDR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## list_all_assets_by_wallet_id > crate::models::ListAllAssetsByWalletIdr list_all_assets_by_wallet_id(wallet_id, context) List All Assets By Wallet ID Through this endpoint customers can obtain information about available assets in one of their wallets, regardless of the blockchain protocol or network, by providing walletId. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **wallet_id** | **String** | Defines the unique ID of the Wallet. | [required] | **context** | Option<**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. | | ### Return type [**crate::models::ListAllAssetsByWalletIdr**](ListAllAssetsByWalletIDR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## list_all_assets_from_all_wallets > crate::models::ListAllAssetsFromAllWalletsR list_all_assets_from_all_wallets(context, limit, offset) List All Assets From All Wallets Through this endpoint customers can obtain information about available assets in all of their wallets, regardless of the blockchain protocol or network. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **context** | Option<**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. | | **limit** | Option<**i64**> | Defines how many items should be returned in the response per page basis. | |[default to 50] **offset** | Option<**i64**> | The starting index of the response items, i.e. where the response should start listing the returned items. | |[default to 0] ### Return type [**crate::models::ListAllAssetsFromAllWalletsR**](ListAllAssetsFromAllWalletsR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## list_deposit_addresses > crate::models::ListDepositAddressesR list_deposit_addresses(blockchain, network, wallet_id, context) List Deposit Addresses Through this endpoint customers can pull a list of Deposit/Receiving Addresses they have already generated. {note}Please note that listing data from the same type will apply pagination on the results.{/note} ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [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. | [required] | **wallet_id** | **String** | Represents the unique ID of the specific Wallet. | [required] | **context** | Option<**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. | | ### Return type [**crate::models::ListDepositAddressesR**](ListDepositAddressesR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## list_supported_tokens > crate::models::ListSupportedTokensR list_supported_tokens(blockchain, network, context, limit, offset) List Supported Tokens Through this endpoint customers can obtain information on multiple tokens at once. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [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. | [required] | **context** | Option<**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. | | **limit** | Option<**i64**> | Defines how many items should be returned in the response per page basis. | |[default to 50] **offset** | Option<**i64**> | The starting index of the response items, i.e. where the response should start listing the returned items. | |[default to 0] ### Return type [**crate::models::ListSupportedTokensR**](ListSupportedTokensR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) ## list_wallet_transactions > crate::models::ListWalletTransactionsR list_wallet_transactions(blockchain, network, wallet_id, context, limit, offset) List Wallet Transactions Through this endpoint customers can list Transactions from and to their Wallet. The data returned will include `transactionId`, `direction` of the transaction - incoming or outgoing, `amount` and more. ### Parameters Name | Type | Description | Required | Notes ------------- | ------------- | ------------- | ------------- | ------------- **blockchain** | **String** | Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc. | [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. | [required] | **wallet_id** | **String** | Represents the unique ID of the specific Wallet. | [required] | **context** | Option<**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. | | **limit** | Option<**i64**> | Defines how many items should be returned in the response per page basis. | |[default to 50] **offset** | Option<**i64**> | The starting index of the response items, i.e. where the response should start listing the returned items. | |[default to 0] ### Return type [**crate::models::ListWalletTransactionsR**](ListWalletTransactionsR.md) ### Authorization [ApiKey](../README.md#ApiKey) ### HTTP request headers - **Content-Type**: Not defined - **Accept**: application/json [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)