Bitcoin Cash
Bitcoin Cash is a blockchain protocol that hard-forked from Bitcoin in August 2017. A hard fork is a split of the existing blockchain, which means that Bitcoin and Bitcoin Cash blockchains were one and the same before the split. The division was a consequence of a debate in the Bitcoin community on how to process a larger amount of transactions per minute. There were two main solutions put forward. The first was to reduce the amount of information included in each block through SegWit2x technology. The second suggestion was to increase the block size, an option suggested by a group of people skeptical of the actual benefits of SegWit2x.
This group of people eventually split up and forked into a new blockchain, namely Bitcoin Cash.
To summarise, the main differences between Bitcoin Cash and Bitcoin are: the block size of 32 MB instead of the 2MB and the scalability solution based on the increased block size rather than on Segwit2x.
Crypto APIs supports Bitcoin Cash mainnet and testnet APIs.
Some Useful Endpoints
Blockchain Information
Get general information about this node.You can get node information like: difficulty, headers, chain work, blocks, transactions, verification progress, etc.
Documentation Response Body: Block Hash
Get Block Hash information.Block Hash endpoint gives you detail information for particular block in the blockchain.
Documentation Response Body: Block Height
Get Block Height information.Block Height endpoint gives you detail information for particular block in the blockchain.
Documentation Response Body: Latest Block
Get Latest Block information.Latest Block Endpoint gives you detail information for the latest block in the blockchain.
Documentation Response Body: Address Details
Get general information about addressesThe default Address Endpoint strikes a general information about addresses.
Documentation Response Body: Multisig Address Details
Get general information about multisig addressesThe Multisig Address Endpoint strikes a general information about a single address that is involved in multisignature addresses.
Documentation Response Body: Generate Address Endpoint
Get Generate Address Endpoint information.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.
Documentation Response Body: Address Transactions Endpoint
Get Address Transactions Endpoint information.The Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.
Documentation Response Body: Confirmed Transactions By Address
Get general information about Confirmed Transactions By AddressThe Address Transactions Endpoint returns all information available about a particular address, including an array of complete transactions.
Documentation Response Body: Multiple Addresses Info Endpoint
Get general information about Multiple Addresses Info EndpointThe Multiple Addresses Info Endpoint strikes a general information about the given addresses in the array.
Documentation Response Body: Transaction API information
Transaction API information Response Body: Transactions Txid Endpoint
Get general information about Transactions Txid EndpointThe Transaction Txid Endpoint returns detailed information about a given transaction based on its id.
Documentation Response Body: Transactions Block Endpoint
Get general information about Transactions Block EndpointThe Transaction Index by Block Endpoint returns detailed information about a list of transactions.
Documentation Response Body: Unconfirmed Transactions Endpoint
Get general information about Unconfirmed Transactions EndpointThe Unconfirmed Transactions Endpoint returns an array of the latest transactions relayed by nodes in a blockchain that haven’t been included in any blocks.
Documentation Response Body: Decode Raw Transactions Endpoint
Get general information Decode Raw Transactions EndpointWe 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.
Documentation Response Body: Creating Transactions Endpoint
Get general information about Creating Transactions EndpointUsing Crypto APIs, you can push transactions to blockchains one of two ways:
Documentation Response Body: Sign Transactions
The Send Transactions Endpoint allows users to sign a transaction.The Sign Transactions Endpoint allows users to sign a raw transaction.
Documentation Response Body: Send Transactions Endpoint
The Sign Transactions Endpoint allows users to sign a raw transaction.Transaction Send Endpoint allows users to broadcast the signed transaction to the Bitcoin blockchain.
Documentation Response Body: New Transaction Endpoint
Get general information about New Transaction EndpointThe 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.
Documentation Response Body: New Transaction Using HDWallet Endpoint
Get general information about New Transaction Using HDWallet EndpointNew Transaction Using HDWallet Endpoint provides the possibility to create, sign and send new transactions using your HDWallet.
Documentation Response Body: Transactions Fee Endpoint
Get general information about Transactions Fee EndpointTransactions Fee Endpoint gives information about the fees for all transactions included in the last 70 blocks.
Documentation Response Body: 
