Blockchain APIs – Blockchain as a service (BaaS)

The returned object contains a litany of information about the blockchain, including its height, the hash of the latest block and more.

Block Hash Endpoint gives you detail information for particular block in the blockchain.

Block Height Endpoint gives you detail information for particular block in the blockchain.

Latest Block Endpoint gives you detail information for the latest block in the blockchain.

The default Address Endpoint strikes a balance between speed of response and data on Addresses. It returns information about the balance (in ETH) and transactions of a specified address.

The Transactions By Address Endpoint returns all transactions specified by the query params: index and limit; The maxim value of limit is 50. The value in the returned transactions in WEI.

The Generate Address endpoint allows you to generate private-public key-pairs along with an associated public address. No information is required with this POST request.

The Generate Account Endpoint allows you to generate private-public key-pairs along with an associated public address encoded in a keyfile. A password and user id are required with this POST request. Keyfiles are stored in a keystore subdirectory on our servers. The critical component of the keyfile, the account’s private key, is always encrypted, and it is encrypted with the password entered when the account was created.

The Nonce Endpoint returns the current nonce of the specified address.

The Transaction Hash Endpoint returns detailed information about a given transaction based on its hash.

The Transaction Index Endpoint by Index, Limit and Block Number returns detailed information about transactions for the block height defined, starting from the index defined up to the limit defined . In the example above index is 0 and limit is 4, therefore the response will be an array of 4 transactions starting from index 0. The highest number for the limit is 50.

The Transaction Index Endpoint by Block Number returns detailed information about a given transaction based on its index and block height.

The Transaction Index Endpoint by Block Hash returns detailed information about a given transaction based on its index and block hash.

Using Crypto APIs, you can push transactions to blockchains one of two ways: Use a third-party library to create your transactions and push raw transactions Use our two-endpoint process outlined below, wherein we generate a TXSkeleton based on your input address, output address, and value to transfer.

Crypto APIs provides the opportunity to locally sign your transaction. If you want to use third-pary tools for signing your raw transactions you can send to the Locally Sign Your Transaction Endpoint only the following data: from address; to address; value.

Once you’ve finished signing the raw transaction locally, send that raw transaction to our Push Raw Transaction Endpoint.

Crypto APIs provides an endpoint for estimating the gas needed for a successful transaction. This is very useful when sending ether to contracts or making a transaction with additional data in it.

Pending Transactions Endpoint makes a call to the EVM and returns all pending transactions. The response might be limited if you lack credits.

Queued Transactions Endpoint makes a call to the EVM and returns all queued transactions. The response might be limited if you lack credits.

Transactions Fee Endpoint gives information about the gas price for the successfull transactions included in the last 1500 blocks

This endpoint retuns the average gas price and gas limit set by the Ethereum Blockchain. At this point for all kinds of deployments the json result will be as follows:

The Deploy Smart Contract Endpoint allows you to push your smart contract to the Ethereum Blockchain. You have to provide the bytecode - compiled to binary solidity code.

In the request url you should provide the address you want to observe and the contract address that created the token. After sending the request you will receive a json object with the name of the token, the amount and its symbol.

In order to transfer tokens from one address to another you should provide the from address, the private key or password (if it is an account stored on our servers), the to address, the contract adress that created the tokens and the amount of tokens you would like to transfer. It is also necessary to provide gas price and gas limit.

In the request url you should provide the address you want to observe. The response will be a json object with a list of all token transactions for the specified address (in DESC order).

In the request url you should provide the address you want to observe. After sending the request you will receive a json object with a list of each transfer for the specified address that includes the following infromation: the contract, the name, symbol and type of the token.

If you have a keystore file or account create on our servers you need to provide the following information: - from address - to address, - callback, - password, - confirmations - after how many confirmations to execute the payment forwarding.

If you want to delete a payment forwarding just specify the uuid of the payment in the url request.

If the request is successful, you’ll receive a JSON (see the response body) and an HTTP Status Code 200.

If the request is successful, you’ll receive a JSON (see the response body) and an HTTP Status Code 200.

Using a partially filled out Event, you can create a Webhook using this resource. Check the Event object description and types of events to understand the available options.

List Webhook Endpoint provides a list with the Webhook for a given user id.

If you want to delete a Webhook just specify the id of the Webhook (the one that was returned in the JSON when creating the Webhook in the url request.

This endpoint deletes all Webhooks for the specified network

The returned object contains a litany of information about the blockchain, including its height, the time/hash of the latest block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the latest block in JSON format, including its height, the number of transactions in it and more. Address API

Address API allows you to look up information about public addresses on the blockchain, generate single-use, low-value key pairs with corresponding addresses.

The returned object returns a list of multisignature addresses in which the queried address is involved in, including balance in BCH and the number of transactions associated with it, and more.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

We also offer support for HD Wallets, which make it easy to manage multiple addresses under a single name. All HD wallet addresses are derived from a single seed. Please see BIP32 for more background on HD wallets. HD Wallets can be created, deleted, and have new addresses generated. However, unlike normal Wallets, addresses cannot be removed.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint returns a string array of active wallet names (both normal оr HD) under the token you queried. You can then query detailed information on individual wallets (via their names) by leveraging the Get Wallet Endpoint.

This endpoint allows you to add public addresses to the wallet name, by POSTing a partially filled out Wallet object. You only need to include the additional addresses in a new addresses array in the object. If successful, it will return the newly modified Wallet, including an up-to-date, complete listing of addresses.

This endpoint allows you to generate a new address associated with the wallet name, similar to the Generate Address Endpoint. If successful, it will returned the newly modified Wallet.

This endpoint allows you to delete an address associated with the wallet name.

This endpoint deletes the Wallet or HD Wallet with the wallet name.

Create XPub Endpoint allows you to create a random extended public key (based on your password), xpriv and wif.

Get XPub Change Addresses Endpoint allows you to get the change(KeyPurpose: Change) addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions

Get XPub receive Addresses Endpoint allows you to get the receive(KeyPurpose: RECEIVE_FUNDS) addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions.

The Transaction Txid Endpoint returns detailed information about a given transaction based on its id.

The Transaction Index by Block Endpoint returns detailed information about a list of transactions.

The Unconfirmed Transactions Endpoint returns an array of the latest transactions relayed by nodes in a blockchain that haven’t been included in any blocks.

We also offer the ability to decode raw transactions without sending propagating them to the network; perhaps you want to double-check another client library or confirm that another service is sending proper transactions.

Using Crypto APIs, you can push transactions to blockchains one of two ways:

The returned object is a hexadecimal string that represents the signed transaction. This hexadecimal is used by the Send Transactions Endpoint in order to broadcast the transaction into the Bitcoin blockchain.

Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain.

The New Transaction Endpoint combines the other three endpoints: Create, Sign and Send Endpoints. Users should provide the inputs and outputs fields with the corresponding data, as well as the fee and the wifs(private ECDSA keys) of the addresses. Therefore, the endpoint creates, signs and broadcasts the new transaction to the Bitcoin Blockchain. For more information, see the examples.

New Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet.

Transactions Fee Endpoint gives information about the fees for all transactions included in the last 70 blocks.

One of the well-known benefits of cryptocurrency is the ability to allow users to partake in online commerce without necessarily requiring extensive setup barriers, like registering new accounts. In that spirit, our Payment Forwarding API is the easiest way to accept—and consolidate—payments securely without forcing your users to create accounts and jump through unnecessary loops. It’s also a generic way to automatically transfer value from one address to another.

First, to create an payment forwarding address, you need to POST a partially filled PaymentForward object to the payment creation endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

When you’re done with a payment forwarding address, you can delete it via its uuid.

Blockchains are highly transactional systems. Many usage patterns require knowing when an event occurs: i.e., when a transaction is included into a block, or when an unconfirmed transaction is relayed through the network. Instead of requiring you to continuously poll resources, we provide push APIs to facilitate those use cases, and support both WebSockets and Webhooks.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using this resource you can list all Webhooks that you have created.

You can delete a Webhook by the Webhook ID using this resource..

This endpoint deletes all Webhooks for the specified network.

The returned object contains a litany of information about the blockchain, including its height, the time/hash of the latest block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the latest block in JSON format, including its height, the number of transactions in it and more. Address API

Address API allows you to look up information about public addresses on the blockchain, generate single-use, low-value key pairs with corresponding addresses.

The returned object returns a list of multisignature addresses in which the queried address is involved in, including balance in BCH and the number of transactions associated with it, and more.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint returns a string array of active wallet names (both normal оr HD) under the token you queried. You can then query detailed information on individual wallets (via their names) by leveraging the Get Wallet Endpoint.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint allows you to add public addresses to the wallet name, by POSTing a partially filled out Wallet object. You only need to include the additional addresses in a new addresses array in the object. If successful, it will return the newly modified Wallet, including an up-to-date, complete listing of addresses.

This endpoint allows you to generate a new address associated with the wallet name, similar to the Generate Address Endpoint. If successful, it will returned the newly modified Wallet.

This endpoint allows you to delete an address associated with the wallet name.

This endpoint deletes the Wallet or HD Wallet with the wallet name.

Create XPub Endpoint allows you to create a random extended public key (based on your password), xpriv and wif.

Get XPub Change Addresses Endpoint allows you to get the change(KeyPurpose: Change) addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions

Get XPub receive Addresses Endpoint allows you to get the receive( addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions.

The Transaction Txid Endpoint returns detailed information about a given transaction based on its id.

The Transaction Index by Block Endpoint returns detailed information about a list of transactions.

The Unconfirmed Transactions Endpoint returns an array of the latest transactions relayed by nodes in a blockchain that haven’t been included in any blocks.

We also offer the ability to decode raw transactions without sending propagating them to the network; perhaps you want to double-check another client library or confirm that another service is sending proper transactions.

Using Crypto APIs, you can push transactions to blockchains one of two ways:

The returned object is a hexadecimal string that represents the signed transaction. This hexadecimal is used by the Send Transactions Endpoint in order to broadcast the transaction into the Bitcoin blockchain.

Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain.

The New Transaction Endpoint combines the other three endpoints: Create, Sign and Send Endpoints. Users should provide the inputs and outputs fields with the corresponding data, as well as the fee and the wifs(private ECDSA keys) of the addresses. Therefore, the endpoint creates, signs and broadcasts the new transaction to the Bitcoin Blockchain. For more information, see the examples.

New Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet.

Transactions Fee Endpoint Get general information about Transactions Fee Endpoint Transactions Fee Endpoint gives information about the fees for all transactions included in the last 70 blocks.

One of the well-known benefits of cryptocurrency is the ability to allow users to partake in online commerce without necessarily requiring extensive setup barriers, like registering new accounts. In that spirit, our Payment Forwarding API is the easiest way to accept—and consolidate—payments securely without forcing your users to create accounts and jump through unnecessary loops. It’s also a generic way to automatically transfer value from one address to another.

First, to create an payment forwarding address, you need to POST a partially filled PaymentForward object to the payment creation endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

When you’re done with a payment forwarding address, you can delete it via its uuid.

Blockchains are highly transactional systems. Many usage patterns require knowing when an event occurs: i.e., when a transaction is included into a block, or when an unconfirmed transaction is relayed through the network. Instead of requiring you to continuously poll resources, we provide push APIs to facilitate those use cases, and support both WebSockets and Webhooks.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using this resource you can list all Webhook that you have created.

You can delete a Webhook by the Webhook ID using this resource..

This endpoint deletes all Webhooks for the specified network.

The returned object contains a litany of information about the blockchain, including its height, the time/hash of the latest block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the block in JSON format, including its height, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block, and more.

The returned object contains information about the latest block in JSON format, including its height, the number of transactions in it and more. Address API

Address API allows you to look up information about public addresses on the blockchain, generate single-use, low-value key pairs with corresponding addresses.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint returns a string array of active wallet names (both normal оr HD) under the token you queried. You can then query detailed information on individual wallets (via their names) by leveraging the Get Wallet Endpoint.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint allows you to add public addresses to the wallet name, by POSTing a partially filled out Wallet object. You only need to include the additional addresses in a new addresses array in the object. If successful, it will return the newly modified Wallet, including an up-to-date, complete listing of addresses.

This endpoint allows you to generate a new address associated with the wallet name, similar to the Generate Address Endpoint. If successful, it will returned the newly modified Wallet.

This endpoint allows you to delete an address associated with the wallet name.

This endpoint deletes the Wallet or HD Wallet with the wallet name.

Create XPub Endpoint allows you to create a random extended public key (based on your password), xpriv and wif.

Get XPub Change Addresses Endpoint allows you to get the change(KeyPurpose: Change) addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions

Get XPub receive Addresses Endpoint allows you to get the receive( addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions.

The Transaction Txid Endpoint returns detailed information about a given transaction based on its id.

The Transaction Index by Block Endpoint returns detailed information about a list of transactions.

The Unconfirmed Transactions Endpoint returns an array of the latest transactions relayed by nodes in a blockchain that haven’t been included in any blocks.

We also offer the ability to decode raw transactions without sending propagating them to the network; perhaps you want to double-check another client library or confirm that another service is sending proper transactions.

Using Crypto APIs, you can push transactions to blockchains one of two ways:

The returned object is a hexadecimal string that represents the signed transaction. This hexadecimal is used by the Send Transactions Endpoint in order to broadcast the transaction into the Bitcoin blockchain.

Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain.

The New Transaction Endpoint combines the other three endpoints: Create, Sign and Send Endpoints. Users should provide the inputs and outputs fields with the corresponding data, as well as the fee and the wifs(private ECDSA keys) of the addresses. Therefore, the endpoint creates, signs and broadcasts the new transaction to the Bitcoin Blockchain. For more information, see the examples.

New Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet.

Transactions Fee Endpoint Get general information about Transactions Fee Endpoint Transactions Fee Endpoint gives information about the fees for all transactions included in the last 70 blocks.

One of the well-known benefits of cryptocurrency is the ability to allow users to partake in online commerce without necessarily requiring extensive setup barriers, like registering new accounts. In that spirit, our Payment Forwarding API is the easiest way to accept—and consolidate—payments securely without forcing your users to create accounts and jump through unnecessary loops. It’s also a generic way to automatically transfer value from one address to another.

First, to create an payment forwarding address, you need to POST a partially filled PaymentForward object to the payment creation endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

When you’re done with a payment forwarding address, you can delete it via its uuid.

Blockchains are highly transactional systems. Many usage patterns require knowing when an event occurs: i.e., when a transaction is included into a block, or when an unconfirmed transaction is relayed through the network. Instead of requiring you to continuously poll resources, we provide push APIs to facilitate those use cases, and support both WebSockets and Webhooks.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using this resource you can list all Webhooks that you have created.

You can delete a Webhook by the Webhook ID using this resource..

This endpoint deletes all Webhooks for the specified network.

The returned object contains a litany of information about the blockchain, including its height, the time/hash of the latest block, and more.

Block Hash endpoint gives you detail information for particular block in the blockchain

Block Height endpoint gives you detail information for particular block in the blockchain

The returned object contains information about the latest block in JSON format, including its height, the number of transactions in it and more. Address API

Address API allows you to look up information about public addresses on the blockchain, generate single-use, low-value key pairs with corresponding addresses.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint returns a string array of active wallet names (both normal оr HD) under the token you queried. You can then query detailed information on individual wallets (via their names) by leveraging the Get Wallet Endpoint.

This endpoint returns a Wallet or HDWallet based on its wallet name

This endpoint allows you to add public addresses to the wallet name, by POSTing a partially filled out Wallet object. You only need to include the additional addresses in a new addresses array in the object. If successful, it will return the newly modified Wallet, including an up-to-date, complete listing of addresses.

This endpoint allows you to generate a new address associated with the wallet name, similar to the Generate Address Endpoint. If successful, it will returned the newly modified Wallet.

This endpoint allows you to delete an address associated with the wallet name.

This endpoint deletes the Wallet or HD Wallet with the wallet name.

Create XPub Endpoint allows you to create a random extended public key (based on your password), xpriv and wif.

Get XPub Change Addresses Endpoint allows you to get the change(KeyPurpose: Change) addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions

Get XPub receive Addresses Endpoint allows you to get the receive( addresses associated with the specified xpub. Since those are hierarchically ordered we provide the arguments from and to - both integeres, in order to be able to get the addresses in the specific positions.

The Transaction Txid Endpoint returns detailed information about a given transaction based on its id.

The Transaction Index by Block Endpoint returns detailed information about a list of transactions.

The Unconfirmed Transactions Endpoint returns an array of the latest transactions relayed by nodes in a blockchain that haven’t been included in any blocks.

We also offer the ability to decode raw transactions without sending propagating them to the network; perhaps you want to double-check another client library or confirm that another service is sending proper transactions.

Using Crypto APIs, you can push transactions to blockchains one of two ways:

The returned object is a hexadecimal string that represents the signed transaction. This hexadecimal is used by the Send Transactions Endpoint in order to broadcast the transaction into the Bitcoin blockchain.

Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain.

The New Transaction Endpoint combines the other three endpoints: Create, Sign and Send Endpoints. Users should provide the inputs and outputs fields with the corresponding data, as well as the fee and the wifs(private ECDSA keys) of the addresses. Therefore, the endpoint creates, signs and broadcasts the new transaction to the Bitcoin Blockchain. For more information, see the examples.

New Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet.

Transactions Fee Endpoint Get general information about Transactions Fee Endpoint Transactions Fee Endpoint gives information about the fees for all transactions included in the last 70 blocks.

One of the well-known benefits of cryptocurrency is the ability to allow users to partake in online commerce without necessarily requiring extensive setup barriers, like registering new accounts. In that spirit, our Payment Forwarding API is the easiest way to accept—and consolidate—payments securely without forcing your users to create accounts and jump through unnecessary loops. It’s also a generic way to automatically transfer value from one address to another.

First, to create an payment forwarding address, you need to POST a partially filled PaymentForward object to the payment creation endpoint.

List Payment Endpoint Get general information about List Payment Endpoint To list your currently active payment forwarding addresses, you can use this endpoint.

To list your currently active payment forwarding addresses, you can use this endpoint.

When you’re done with a payment forwarding address, you can delete it via its uuid.

Blockchains are highly transactional systems. Many usage patterns require knowing when an event occurs: i.e., when a transaction is included into a block, or when an unconfirmed transaction is relayed through the network. Instead of requiring you to continuously poll resources, we provide push APIs to facilitate those use cases, and support both WebSockets and Webhooks.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using a partially filled out Event, you can create a Webhook using this resource.

Using this resource you can list all Webhooks that you have created.

You can delete a Webhook by the Webhook ID using this resource.

This endpoint deletes all Webhooks for the specified network.

The returned object contains a litany of information about the blockchain, including its height, the hash of the latest block and more.

Block Hash Endpoint gives you detail information for particular block in the blockchain

The returned object contains information about the block in JSON format, including its height, the total amount of wei transacted within it, the number of transactions in it, transaction hashes listed in the canonical order in which they appear in the block and more.

The returned object contains information about the latest block in JSON format, including its height, the total amount of wei transacted within it, the number of transactions in it and more.

The default Address Endpoint strikes a balance between speed of response and data on Addresses. It returns information about the balance (in ETC) and transactions of a specified address.

The Transactions By Address Endpoint returns all transactions specified by the query params: index and limit; The maxim value of limit is 50. The value in the returned transactions in WEI.

The Generate Address endpoint allows you to generate private-public key-pairs along with an associated public address. No information is required with this POST request.

The Generate Account Endpoint allows you to generate private-public key-pairs along with an associated public address encoded in a keyfile. A password and user id are required with this POST request. Keyfiles are stored in a keystore subdirectory on our servers. The critical component of the keyfile, the account’s private key, is always encrypted, and it is encrypted with the password entered when the account was created.

The Nonce Endpoint returns the current nonce of the specified address.

The Transaction Hash Endpoint returns detailed information about a given transaction based on its hash.

The Transaction Index Endpoint by Index, Limit and Block Number returns detailed information about transactions for the block height defined, starting from the index defined up to the limit defined . In the example above index is 0 and limit is 4, therefore the response will be an array of 4 transactions starting from index 0. The highest number for the limit is 50.

The Transaction Index Endpoint by Block Hash returns detailed information about a given transaction based on its index and block hash.

The Transaction Index Endpoint by Block Number returns detailed information about a given transaction based on its index and block height.

Use a third-party library to create your transactions and push raw transactions Use our two-endpoint process outlined below, wherein we generate a TXSkeleton based on your input address, output address, and value to transfer.

Crypto APIs provides the opportunity to locally sign your transaction. If you want to use third-pary tools for signing your raw transactions you can send to the Locally Sign Your Transaction Endpoint only the following data: from address; to address; value.

Pending Transactions Endpoint makes a call to the EVM and returns all pending transactions. The response might be limited if you lack credits.

Once you’ve finished signing the raw transaction locally, send that raw transaction to our Push Raw Transaction Endpoint.

Queued Transactions Endpoint makes a call to the EVM and returns all queued transactions. The response might be limited if you lack credits.

Crypto APIs provides an endpoint for estimating the gas needed for a successful transaction. This is very useful when sending etc to contracts or making a transaction with additional data in it.

Transactions Fee Endpoint gives information about the gas price for the successful transactions included in the last 1500 blocks.

This endpoint retuns the average gas price and gas limit set by the Ethereum Classic Blockchain.

In the request url you should provide the address you want to observe and the contract address that created the token. After sending the request you will receive a json object with the name of the token, the amount and its symbol.

In order to transfer tokens from one address to another you should provide the from address, the private key or password (if it is an account stored on our servers), the to address, the contract address that created the tokens and the amount of tokens you would like to transfer.

If you have a keystore file/account create on our servers you need to provide the following information: - from address - to address, - callback, - password, - confirmations - after how many confirmations to execute the payment forwarding - gasPrice (Optional) - gasLimit (Optional)

If you want to delete a payment forwarding just specify the uuid of the payment in the url request.

If the request is successful, you’ll receive a JSON and an HTTP Status Code 200.

If the request is successful, you’ll receive a JSON (see the response body) and an HTTP Status Code 200.

Using a partially filled out Event, you can create a Webhook using this resource. Check the Event object description and types of events to understand the available options.

List Webhook Endpoint provides a list with the webhooks for a given user id.

If you want to delete a webhook just specify the id of the webhook in the url request.

This endpoint deletes all Webhooks for the specified network.

The returned object contains a litany of information about the blockchain, including its height, the time of the latest block, the number of transactions in the latest block, total trades and the total count of all omni transactions.

The returned object contains information about the specified address, all the tokens that it posses, their value and name.

The returned object contains information about the address, including the number of transactions associated with it, and the corresponding full transaction records in descending order by blocktime.

This endpoint allows users to create transactions type Simple Send within the Omni Layer.

The returned object is a hexadecimal string that represents the signed transaction. This hexadecimal is used by the Send Transactions Endpoint in order to broadcast the transaction into the Bitcoin blockchain.

Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain. If broadcasting is successful, you’ll receive a JSON with the hash of the unconfirmed transaction.

The New Transaction Endpoint combines the other three endpoints: Create, Sign and Send Endpoints. In other words, this endpoint directly broadcasts the newly created transaction to the Bitcoin blockchain. For more information, see the examples.

New Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet. The mandatory fields are: walletName, password, from, to, value, fee and propertyID. There are a two optional fields, such as: data and locktime.

The returned object contains information about the transaction in JSON format, including its block information, the total amount transacted with it, the from and to addresses, and more.

The Transaction Index by Block Endpoint returns detailed information about a list of transactions. The endpoint is useable both with block height and block hash. index and limit query parameters might also be used, as their default values are, as follows: 0, 1. Therefore, if none is specified the returned object will be the first transaction (the coinbase transaction) included in the block.

The Transaction by Property Id Endpoint returns detailed information about a list of transactions by property. index and limit query parameters might also be used, as their default values are, as follows: 0, 50. The number 31 stands for Tether.

Zilliqa is a new blockchain platform that is designed to scale in an open, permission-less distributed network securely.

General information about a blockchain is available by GET-ing the base resource.

Block Hash Endpoint gives you detail information for particular block in the blockchain

Block Height Endpoint gives you detailed information for particular block in the blockchain

Latest Block Endpoint gives you detailed information for the latest block in the blockchain

The default Address Endpoint strikes a balance between response time and data on Addresses. It returns information about the balance (in ZIL) and transactions of a specific address.

The Transactions By Address Endpoint returns all transactions specified by the query params: index and limit; The maximum value of limit is 50. The value in the returned transactions in ZIL.

The Generate Address endpoint allows you to generate private-public key-pairs along with an associated public address. No information is required with this POST request.

The Transaction Hash Endpoint returns detailed information about a given transaction based on its hash.

The Transaction Index Endpoint by Index, Limit and Block Number returns detailed information about transactions for the block height defined, starting from the index defined up to the limit defined . In the example above index is 0 and limit is 4, therefore the response will be an array of 4 transactions starting from index 0. The highest number for the limit is 50.

The Transaction Index Endpoint by Block Number returns detailed information about a given transaction based on its index and block height.

The Transaction Index Endpoint by Block Hash returns detailed information about a given transaction based on its index and block hash.

General information about a blockchain is available by GET-ing the base resource.

Block Hash Endpoint gives you detail information for particular block in the blockchain.

Block Height Endpoint gives you detailed information for particular block in the blockchain

Latest Block Endpoint gives you detailed information for the latest block in the blockchain

The default Address Endpoint strikes a balance between response time and data on Addresses. It returns information about the balance (in XRP) and transactions of a specific address.

The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.

The Transaction Hash Endpoint returns detailed information about a given transaction based on its hash.

The Transaction Index Endpoint by Index, Limit and Block Number returns detailed information about transactions for the block height defined, starting from the index defined up to the limit defined .

The Transaction Index Endpoint by Block Number returns detailed information about a given transaction based on its index and block height.

The Transaction Index Endpoint by Block Hash returns detailed information about a given transaction based on its index and block hash.

Transaction Send Endpoint allows users to broadcast the signed transaction to the XRP Ledger.

Using a partially filled out Event, you can create a Webhook using this resource. Check the Event object description and types of events to understand the available options.

List Webhook Endpoint provides a list with the webhooks for a given user id.

If you want to delete a webhook just specify the id of the webhook (the one that was returned in the JSON when creating the webhook) in the url request.