Chains Quickstart

This docs section provides the list of all chains available on the Web3 API platform (opens in a new tab). Each chain in the list has the following information structure:

Overview —— Networks —— Adding to MetaMask —— Methods —— API Querying

• Overview — chain description based on official docs with quicklinks to chain's website, docs, and GitHub.
• Networks — networks (Mainnet/Testnet) and protocols (HTTPS/WSS) we support for each chain.
• Adding to MetaMask — using Ankr as the blockchain provider for MetaMask.
• Methods — supported (link to the chain's API Reference) and unsupported methods.
• API Querying — code snippets with basic requests in various languages and the corresponding JSON responses.

Chains supported

Find the chain you require and go to its docs section by clicking it.

Aptos

Aptos API is available on Web3 API platform (opens in a new tab).

The Aptos blockchain, designed with scalability, safety, reliability, and upgradability as key principles, to address blockchain challenges, such as frequent outages, high costs, low throughput limits, and security concerns. The Aptos blockchain has been developed over the past three years by over 350+ developers across the globe. It offers new and novel innovations in consensus, smart contract design, system security, performance, and decentralization. The combination of these technologies will provide a fundamental building block to bring web3 to the masses.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS)
• Testnet (HTTPS)

API methods

For Aptos, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

/v1/spec, /v1/-/healthy

API querying

Request example

curl -X GET https://rpc.ankr.com/http/aptos/v1/ \
-H 'Content-Type: application/json'

Response example

{
  "chain_id": 0,
  "epoch": "32425224034",
  "ledger_version": "32425224034",
  "oldest_ledger_version": "32425224034",
  "ledger_timestamp": "32425224034",
  "node_role": "validator",
  "oldest_block_height": "32425224034",
  "block_height": "32425224034",
  "git_hash": "string"
}

Arbitrum

Arbitrum API is available on Web3 API platform (opens in a new tab).

Arbitrum is a side chain that runs parallel to Ethereum Mainnet. Also known as a Layer 2 (L2) scaling solution, Arbitrum improves transaction speeds and cost compared to the mainnet, making it an excellent solution for Ethereum developers.

By the Arbitrum we mean Arbitrum One which is the flagship Arbitrum mainnet chain; it is an Optimistic Rollup chain running on top of Ethereum Mainnet, and is open to all users. In an upgrade on 8/31, the Arbitrum One chain was upgraded to use the Nitro (opens in a new tab) tech stack, maintaining the same state.

Official quick links:

• Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)
• Community treasury address (opens in a new tab) (0x8C316E77c4D4aBc461a074cf68c04DD666c57b42)

Networks

• Mainnet (HTTPS and WSS)

API methods

For Arbitrum, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/arbitrum \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0x2484729"
}

Arbitrum Nova

Arbitrum Nova API is available on Web3 API platform (opens in a new tab).

Arbitrum Nova offers an ultra-low transaction costs with high security. Nova powers dapps with high transaction volumes that seek to drive costs even lower.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)

API methods

For Arbitrum Nova, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/arbitrumnova \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0x257932"
}

Avail

Avail API is available on Web3 API platform (opens in a new tab).

Avail is a Web3 infrastructure layer that allows modular execution layers to scale and interoperate in a trust minimized way.

A foundational Data Availability (DA) layer, Nexus interoperability layer, and Fusion Security network layer come together to form the Unification Layer.

• The DA layer is a highly optimized, low-level layer, specifically constructed for data availability. This is the deepest blockchain layer, with the minimal functionality required to build cross-ecosystem interoperability on top.
• Nexus acts as a light but powerful proof aggregation and sequencer selection ZK rollup on top of Avail, allowing for cross-rollup and cross-ecosystem settlement.
• Fusion Security enables a basket of tokens to pool their crypto-economic security to serve and secure the Avail network.

Avail's mission is to streamline the rollup experience, offering a unified, efficient platform for both users and developers from any ecosystem. This vertically integrated stack aims to dissolve the growing pains and user fragmentation experienced today, enabling Rollups to seamlessly access users and liquidity across the entire blockchain landscape.

The Turing Testnet is live and marks Avail's final and definitive pre-Mainnet testing environment, aimed at vetting Mainnet deployments, executing extensive stress tests, and assessing network topologies for scalability and resilience.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Turing Testnet (HTTPS and WSS)

API methods

For Avail, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

state_getMetadata, state_getPairs, state_traceBlock, state_trieMigrationStatus, state_subscribeStorage, state_unsubscribeStorage, state_queryStorage, sync_state_genSyncSpec, system_accountNextIndex, system_addLogFilter, system_addReservedPeer, system_health, system_localListenAddresses, system_localPeerId, system_name, system_nodeRoles, system_peers, system_properties, system_removeReservedPeer, system_reservedPeers, system_resetLogFilter, system_syncState, system_unstable_networkState, system_version,

account_*, babe_*, mmr_*, dev_*, offchain_*, author_*

API querying

Request example

curl -X POST https://rpc.ankr.com/avail_turing_testnet \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "id": 1,
      "method": "chain_getBlock",
      "params": []
}'

Response example

{
    "jsonrpc": "2.0",
    "result": {
        "block": {
            "header": {
                "parentHash": "0x32d67a9e5843dd8527bf0e2ec1f4c6d2f8642ef264348ef7d610575619a5b6e8",
                "number": "0x49993",
                "stateRoot": "0x7d0860d48e20e42886aeac479dd339d1f75387d3be844a490ca1734efd430213",
                "extrinsicsRoot": "0x07d2cb3154a4bc3ff485d0101bb1cba8045bf1bd74a34a977cc2672a41e76596",
                "digest": {
                    "logs": [
                        "0x0642414245b5010359000000757a1e0500000000841bf8fb61a548ec94caba8ddedcf85e02de0110990ffe3c4216277ee0b9734a9b966b69d9025691e82043d9a647ce917871b1b2d2082afc3ce3b195c96e1c039b2e312d9028cf976284d61c41f1069b1df154b5e6b6bef9ad4455dd24ea160d",
                        "0x05424142450101c2be2a753a256b1261e00d5d31a20befa735767d5debe27edfff52149e4ce53398135479d97a0e594a2160cf78b3743ca42899138b0c5b58334bc7c4d0217080"
                    ]
                },
                "extension": {
                    "V3": {
                        "appLookup": {
                            "size": 114,
                            "index": [
                                {
                                    "appId": 36,
                                    "start": 0
                                }
                            ]
                        },
                        "commitment": {
                            "rows": 1,
                            "cols": 128,
                            "commitment": [
                                128,
                                27,
                                216,
                                161
                            ],
                            "dataRoot": "0x67e432157400275ba4e6e7c9d61312afa5cbbea68d8b718fa8be3038980a9970"
                        }
                    }
                }
            },
            "extrinsics": [
                "0x280403000ba0f41eed8f01",
                "0xc90384007ce8ccf46bbdf7561f0d1419857dab91bfbda9866d564c2c5cfe43210a75db310122850737c933478016ee92ddcbd1eda470ead30b6a7938adba396b9e51922949b1bba1bf56ca8bd67f2241b1240fa1f2bd18f07b42111fe70f9f386b78f66f87040162760100000001020c0603004e558a63713b227cb661a5cb639c5bea499bd00039d7dabe16cb891e8fc2025213000064a7b3b6e00d06030006aa84733a1b39c3cc83586e589fd6bb82228321e1f75d4e2bc3af8d4957785213000064a7b3b6e00d0603003a1e5289c81ff9dfd53cf55e64aaaee9aeb31e5ae43c9679de15a841b406521d13000064a7b3b6e00d"
            ]
        },
        "justifications": null
    },
    "id": 1
}

Avalanche

Avalanche API is available on Web3 API platform (opens in a new tab).

Avalanche is an open-source platform for launching decentralized applications and enterprise blockchain deployments in one interoperable, highly scalable ecosystem. Avalanche is the first decentralized smart contracts platform built for the scale of global finance, with near-instant transaction finality. Ethereum developers can quickly build on Avalanche as Solidity works out-of-the-box.

Avalanche is an ecosystem that features three built-in blockchains: Exchange Chain (X-Chain) (opens in a new tab), Platform Chain (P-Chain) (opens in a new tab), and Contract Chain (C-Chain) (opens in a new tab).

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet / Fuji Testnet:
  • Standard EVM API (HTTPS and WSS)
  • X-Chain (HTTPS)
  • P-Chain (HTTPS)
  • C-Chain (HTTPS)

Add networks to MetaMask

Using Ankr as the blockchain provider for MetaMask makes user interaction on Web3 not just easy and slick but also PRIVATE. We DON'T collect users' blockchain addresses — end of the story. Feel free to check our terms (opens in a new tab) and privacy policy (opens in a new tab) to be sure.

For MetaMask to interact with Avalanche through Ankr's infrastructure, add a required Avalanche network either via Web3 API platform's or MetaMask's UI.

Via Web3 API platform

To be added soon.

Via MetaMask

To add Avalanche Mainnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Avalanche Mainnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/avalanche/.
   • Chain ID: 43114.
   • Currency symbol: AVAX.
   • Block explorer URL: https://snowtrace.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Avalanche Mainnet.

To add Avalanche Fuji Testnet, follow these steps:

1. In MetaMask extension, click Networks (drop-down menu) > Add network to open Settings.

2. In the Add a network pane, click Add a network manually, then enter the network details and click Save:

   • Network name: Avalanche Fuji Testnet by Ankr RPC.
   • New RPC URL: https://rpc.ankr.com/avalanche_fuji/.
   • Chain ID: 43113.
   • Currency symbol: AVAX.
   • Block explorer URL: https://testnet.snowtrace.io/.

Congrats — you've just added Ankr as the blockchain provider for MetaMask to interact with Avalanche Fuji Testnet.

API methods

For Avalanche, we support blockchain interaction via the following methods:

• Standard EVM methods
• P-Chain methods
• C-Chain methods
• X-Chain methods

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate, net_peerCount,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*,

avm.createAddress, avm.exportKey, avm.importKey, avm.export, avm.import, avm.mint, avm.createFixedCapAsset, avm.createVariableCapAsset, avm.createNFTAsset, avm.mintNFT, avm.listAddresses, avm.send, avm.sendMultiple, avm.sendNFT, wallet.send, wallet.sendMultiple, wallet.issueTx, avax.export, avax.exportAVAX, avax.exportKey, avax.import, avax.importAVAX, avax.importKey,

platform.addDelegator, platform.addValidator, platform.addSubnetValidator, platform.createAddress, platform.createBlockchain, platform.createSubnet, platform.exportAVAX, platform.exportKey, platform.importAVAX, platform.importKey, platform.listAddresses

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example (Standard EVM)

curl -X POST https://rpc.ankr.com/avalanche \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example (Standard EVM)

{
  "jsonrpc":"2.0",
  "result":"0x155ea63",
  "id":1
}

Request example (P-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-p' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"platform.getBalance",
    "params" :{
      "address":"P-custom18jma8ppw3nhx5r4ap8clazz0dps7rv5u9xde7p"
    }
}'

Response example (P-Chain)

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "txID": "NUPLwbt2hsYxpQg4H2o451hmTWQ4JZx2zMzM4SinwtHgAdX1JLPHXvWSXEnpecStLj"
  }
}

Request example (C-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-c' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"avax.getAtomicTx",
    "params" : {
        "txID":"2GD5SRYJQr2kw5jE73trBFiAgVQyrCaeg223TaTyJFYXf2kPty",
        "encoding": "hex"
    }
}'

Response example (C-Chain)

{
  "jsonrpc": "2.0",
  "result": {
    "tx": "0x000000000000000030399d0775f450604bd2fbc49ce0c5c1c6dfeb2dc2acb8c92c26eeae6e6df4502b19d891ad56056d9c01f18f43f58b5c784ad07a4a49cf3d1f11623804b5cba2c6bf000000018212d6807a0ec9c1b26321418fe7a548180b5be728ce53fe7e98ab5755ed316100000001dbcf890f77f49b96857648b72b77f9f82937f28a68704af05da0dc12ba53f2db00000005000003a352a382400000000100000000000000018db97c7cece249c2b98bdc0226cc4c2a57bf52fc000003a3529edd17dbcf890f77f49b96857648b72b77f9f82937f28a68704af05da0dc12ba53f2db000000010000000900000001ead19377f015422fbb8731204fcf6d6879dd05146c2d5b5594e2fea2cb420b2f40bd457b71e279e547790b28fe5482f278c76cf39b2dce5c2e6c53352fe6827d002cc7d20d",
    "encoding": "hex",
    "blockHeight": "1"
  },
  "id": 1
}

Request example (X-Chain)

curl -X POST 'https://rpc.ankr.com/avalanche-x' \
-H 'Content-Type: application/json' \
-d '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"avm.getAddressTxs",
    "params" : {
      "address":"X-avax1dp6707ka34puejwg7ntnenxry98h37yvsqsm7f",
      "assetID":"AVAX",
      "pageSize":20
    }
}'

Response example (X-Chain)

{
  "jsonrpc": "2.0",
  "result": {
    "txIDs": ["SsJF7KKwxiUJkczygwmgLqo3XVRotmpKP8rMp74cpLuNLfwf6"],
    "cursor": "1"
  },
  "id": 1
}

B2 Network

B² Network API is available on Web3 API platform (opens in a new tab).

The B² Network is an advanced Layer-2 solution designed to enhance transaction speed, reduce costs, and broaden application diversity without compromising security. It is notable for being the first zero-knowledge proof verification commitment rollup on Bitcoin.

Key Features:

• Zero-Knowledge Proof Verification: Utilizes zero-knowledge proof technology to ensure transactional privacy and security, allowing for the verification of transactions without revealing the underlying data.

• Rollup Technology: Processes multiple off-chain transactions and rolls them into a single on-chain transaction, significantly increasing efficiency and reducing costs.

• Turing-Complete Smart Contracts: Supports Turing-complete smart contracts, enabling complex computations and a wide range of decentralized applications (dApps) to run off-chain with enhanced performance.

• Gate Commitment and Challenge-Response Mechanism: Integrates gate commitment and challenge-response mechanisms, leveraging Taproot on Bitcoin to ensure secure and private transaction confirmations.

• EVM-Compatibility: The B² Network is compatible with the Ethereum Virtual Machine (EVM), allowing it to run Ethereum-based smart contracts and dApps. This compatibility enables developers to use existing Ethereum tools, libraries, and standards while benefiting from the B² Network's enhanced features.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet (HTTPS and WSS)

API methods

For B² Network, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/b2 \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
  "jsonrpc":"2.0",
  "id":1,
  "result":"0x21194c"
}

Bahamut

Bahamut API is available on Web3 API platform (opens in a new tab).

Bahamut is an EVM-based, Layer 1 public blockchain designed to improve block reward distribution by incorporating validator activity into the consensus algorithm.

Key Features:

• EVM-Compatible: Fully compatible with Ethereum smart contracts.
• Layer 1 Blockchain: Operates independently with its own infrastructure.
• Consensus Mechanism: Proof of Stake and Activity (PoSA)

Bahamut introduces a unique Proof of Stake and Activity (PoSA) consensus mechanism, combining traditional PoS with an activity parameter based on the gas used by a validator's smart contracts.

• Proof of Stake (PoS): Validators are selected based on their stake in the network.
• Activity Parameter: Measures and rewards validators based on their smart contract activity, influencing their chances of proposing new blocks.

Benefits:

• Encourages Active Participation: Rewards validators for both stake and activity.
• Fair Reward Distribution: Ensures a more equitable distribution of block rewards.
• Improved Efficiency: Promotes faster transaction processing and smart contract execution.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet (HTTPS and WSS)

API methods

For Bahamut, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/bahamut \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x2c599a"
}

Base

Base API is available on Web3 API platform (opens in a new tab).

Base is a secure, low-cost, developer-friendly Ethereum L2 built to bring the next billion users to web3.

Base is built on the Bedrock (opens in a new tab) release of the OP Stack (opens in a new tab), which is designed from the ground up to be as close to Ethereum as possible. Because of this, there are very little differences when it comes to building on Base and Ethereum.

However, there are still some minor discrepancies between the behavior of Base and Ethereum that you should be aware of when building apps on top of Base.

These minor differences include:

• Opcodes (opens in a new tab)
• Blocks (opens in a new tab)
• Network specifications (opens in a new tab)
• Transaction costs (opens in a new tab)

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS and WSS)
• Testnet:
  • Sepolia (HTTPS and WSS)

API methods

For Base, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/base \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc":"2.0",
      "method":"eth_blockNumber",
      "params": [],
      "id":1
    }'

Response example

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0x459996"
}

Berachain

Berachain API is available on Web3 API platform (opens in a new tab).

Berachain is a high-performance EVM-compatible blockchain built on Proof-of-Liquidity consensus. Proof-of-Liquidity is a novel consensus mechanism that aims to align network incentives, creating strong synergy between Berachain validators and the ecosystem of projects. Berachain's technology is built on Polaris, a high-performance blockchain framework for building EVM-compatible chains on-top of the CometBFT consensus engine.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Testnet (HTTPS and WSS)

API methods

For Berachain, we support blockchain interaction via all the applicable methods except for those listed as unsupported.

Unsupported

HTTPS:

eth_newFilter, eth_getFilterChanges, eth_coinbase, eth_hashrate, eth_mining, eth_getWork,eth_submitWork, eth_submitHashrate, net_peerCount, eth_newBlockFilter, eth_newPendingTransactionFilter, eth_uninstallFilter, eth_getFilterLogs,

debug_*, personal_*, admin_*, clique_*, les_*, miner_*, engine_*, parity_*

WSS:

txpool_content, txpool_inspect, txpool_status, txpool_contentFrom

API querying

Request example

curl -X POST https://rpc.ankr.com/berachain_testnet \
-H 'Content-Type: application/json' \
-d '{
      "jsonrpc": "2.0",
      "method": "eth_blockNumber",
      "params": [],
      "id": 1
    }'

Response example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x26a494"
}

Bitcoin

Bitcoin API is available on Web3 API platform (opens in a new tab).

Bitcoin API provides the means for communication with the Bitcoin’s public ledger.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)

Networks

• Mainnet (HTTPS)
• Signet Testnet (HTTPS)

API methods

For Bitcoin, we support blockchain interaction via the following interfaces:

• Bitcoin API native methods
• Blockbook API methods

Unsupported

Bitcoin's HTTPS:

savemempool, verifychain, getmemoryinfo, getrpcinfo, gettransaction, help, logging, stop, uptime, getblocktemplate, getmininginfo, getnetworkhashps, pruneblockchain, generateblock, generatetoaddress, generatetodescriptor, prioritisetransaction, submitblock, submitheader, addnode, clearbanned, disconnectnode, getaddednodeinfo, getconnectioncount, getnettotals, getnetworkinfo, getnodeaddresses, getpeerinfo, listbanned, ping, setban, setnetworkactive, signrawtransactionwithkey, createmultisig, getdescriptorinfo, signmessagewithprivkey, abandontransaction, abortrescan, addmultisigaddress, backupwallet, bumpfee, createwallet, dumpprivkey, dumpwallet, encryptwallet, getaddressesbylabel, getbalance, getbalances, getnewaddress, getrawchangeaddress, getreceivedbyaddress, getreceivedbylabel, getunconfirmedbalance, getwalletinfo, importaddress, importdescriptors, importmulti, importprivkey, importprunedfunds, importpubkey, importwallet, keypoolrefill, listaddressgroupings, listlabels, listlockunspent, listreceivedbyaddress, listreceivedbylabel, listtransactions, listsinceblock, listunspent, listwalletdir, listwallets, loadwallet, lockunspent, psbtbumpfee, removeprunedfunds, rescanblockchain, send, sendmany, sendtoaddress, sethdseed, setlabel, setwalletflag, signmessage, settxfee, signrawtransactionwithwallet, unloadwallet, upgradewallet, walletcreatefundedpsbt, walletlock, walletpassphrase, walletpassphrasechange, walletprocesspsbt, deriveaddresses, fundrawtransaction, scantxoutset, preciousblock, gettxoutsetinfo

Blockbook API:

• All WebSocket methods
• All socket.io methods

API querying

Request example

curl -X POST https://rpc.ankr.com/btc \
-d '{
      "id": "hmm",
      "method": "getindexinfo",
      "params": []
}'

Response example

{
    "result": {
        "txindex": {
            "synced": true,
            "best_block_height": 843277
        },
        "basic block filter index": {
            "synced": true,
            "best_block_height": 843277
        }
    },
    "error": null,
    "id": "hmm"
}

Bitlayer

Bitlayer API is available on Web3 API platform (opens in a new tab).

Bitlayer is the first Bitcoin security-equivalent layer 2 based on BitVM. It consists of an EVM compatible chain/sequencer that can map BTC ecological assets and facilitate the entry of BTC users.

Official quick links: Website (opens in a new tab), Docs (opens in a new tab), GitHub (opens in a new tab)