Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Aptos Network API Reference for seamless interaction with APT nodes, enabling fast, secure, and scalable transactions on a next-generation Layer 1 blockchain.
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Arbitrum Network API Reference for efficient interaction with ARB nodes, enabling fast, low-cost Layer 2 scaling solutions for Ethereum with high throughput and secure smart contracts.
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
GetBlock offers scalable plans tailored to developers and businesses, providing flexible solutions for both small projects and high-traffic platforms.
GetBlock offers flexible plans and features to support developers and businesses at any stage, from small projects to high-traffic platforms. This section covers available plans, scaling features, and managing subscriptions and payments.
To start using GetBlock's services, you need to register an account. You’ll be ready to go in just a few clicks!
Register with Email
Enter your name and email address, then verify your email to activate the account.
Sign in via Google
Google will share your name, email, language preferences, and profile picture with GetBlock.
Connect with MetaMask
Use a MetaMask wallet browser extension to sign up – no email or password required. If you don’t have a wallet extension installed, you’ll be prompted to add one.
Sign up with GitHub
Use your GitHub credentials to set up an account.
Once you've created an account and signed in, you'll be directed to the GetBlock Dashboard. Here, you can create endpoints, monitor your usage plan, and access statistics.
Find your user ID located in the ‘Account Settings’ section or simply click your account icon to view it. Please use it when contacting GetBlock’s team so we can identify your account and help you faster.
Compare GetBlock's subscription options to find the one that fits your project.
GetBlock offers three main service options—Shared Nodes, Dedicated Nodes, and Enterprise Solutions. This page provides a high-level overview of these services.
Shared nodes operate on a resource-sharing model, where multiple clients access the same underlying node infrastructure maintained by GetBlock.
Our Shared Nodes deliver the perfect balance between affordability and performance:
Flexible pricing: Options range from a free to high-volume plans — accessible for individual developers and smaller teams while supporting the scaling needs of growing dApps.
Consistent performance: Each plan enforces a Requests Per Second (RPS) limit, preventing individual spikes from impacting overall quality.
Tiered support levels: Support options adapt to your requirements, from basic help to priority support when you need it most.
Multi-chain accessibility: Prototype, test, and deploy applications across different networks without the complexities of connecting to each blockchain individually.
This option is ideal for developers and teams looking for reliable connectivity to various blockchain networks without the higher costs of dedicated server resources.
A Dedicated Node is a private RPC server deployed solely for your use case. That means consistent throughput, no API rate throttling due to other users, and better uptime guarantees.
If your project demands the fastest, most reliable blockchain infrastructure, a Dedicated Node from GetBlock is a perfect choice.
This option is ideal for users that require high performance, full control over node configuration, and a flawless connection to the blockchain without any limitations:
Mission-critical reliability: Maximized uptime and robust failover mechanisms for even more reliable service.
Unlimited usage: No per-second request caps or CU tracking.
Low latency: With servers available in Europe, Asia, and the USA, choose the optimal server location to minimize latency and enhance performance for your users
Fully customizable: Complete control over your node configurations, including access to archive data.
Predictable pricing:
Full Node: $1,000/month;
Archive Node: $1,500/ month.
Expert support: 24/7 coverage and immediate issue resolution.
This option is designed to meet the needs of organizations operating at scale or applications that require extra resources, features, and dedicated support.
What’s included:
99.9% uptime guarantee
Customizable node configurations and integrations
Performance optimization via load balancers
Advanced analytics and alert systems
Priority assistance from GetBlock experts
Visit the and click on the 'Dashboard' button in the upper-right corner, or use .
During registration, you will be asked to accept our and .
You can explore detailed pricing and plans from your dashboard in the “Pricing” section or via .
Cost efficiency: Benefit from our pricing model based on , so you only pay for the resources needed for your current workload.
Visit the to learn more about how we tailor services to fit complex, high-demand environments.
Welcome to GetBlock.io! We make it easy for developers and businesses to connect to 50+ blockchain networks.
With our tools and services, you can focus on building your Web3 project without worrying about the technical details of setting up and managing blockchain nodes.
From DeFi apps and NFT platforms to analytics tools, AppChains, and more, GetBlock provides the infrastructure to help you build, test, and scale your blockchain-powered solutions.
Plug-and-Play access
Our ready-to-use blockchain nodes and APIs help you get started immediately.
99.9% uptime Reliable 24/7 connection to multiple blockchain networks.
Multi-chain support
Connect to Bitcoin, Ethereum, BNB Chain, Polygon, Solana, TON, and 50+ other networks. (And we support new protocols before anyone else!)
Flexible plans
From free access to enterprise-grade solutions, we’ve got options for every stage of your project.
Custom solutions
Need something unique? We can build tailored solutions for your specific blockchain needs.
24/7 Expert support
Our team is here to help with integrations, troubleshooting, and scaling.
Get started with our most in-demand blockchain networks.
GetBlock provides access to over 50 blockchains. CU and rate limits depend on the selected plan.
This guide explains how limits work across all available plans, helping you understand what’s included and how to choose the option that best fits your current workload and future growth.
Shared Nodes operate on a system of limits defined by Compute Units (CUs) and Requests Per Second (RPS). Each plan also determines how many access tokens you can generate.
With Dedicated Nodes, you’re not limited by CUs or RPS.
GetBlock’s shared node service is subject to several usage limits. These are the key limits that directly affect costs and performance:
CU (Compute Units): Measures the computational effort required to process requests. Different shared node plans include a varying number of CUs that you can use in a month.
RPS (Requests Per Second): Each plan enforces a maximum number of requests you can send every second. While you’re not billed per request, staying within this limit is critical to maintaining optimal service quality.
Access Tokens: Access tokens are unique identifiers used to authenticate your connection to GetBlock’s node infrastructure, generated when you create an endpoint. The limitation on your plan determines how many of these access tokens (and therefore endpoints) you can create.
$0
$49
$499
from $999
CU Allocation
50k/day
50M/month
600M/month
Custom
RPS Limit
5 RPS
25 RPS
200 RPS
Custom
Access Tokens
2
10
50
Custom
Extra CU Purchase
❌
✅
✅
✅
If you don’t use all your allocated CUs within a month, the unused amount will carry over to the next month as long as your subscription is active and renewed. If your subscription expires or is not renewed on time, the remaining CUs will be lost.
If your demand exceeds the included limits, you can purchase extra CU packages. This means that even within a given plan, there’s room for scaling without an immediate need to move to a higher tier.
Our Dedicated Node service is perfect for teams and projects that demand absolute freedom from rate limits and CU monitoring.
CU: Unlimited
Rate: Unlimited
To see the full comparison table, navigate to .
The plan is ideal if you’re just starting out and do not have complex calls or large request volumes.
CU: 50,000/day
Rate: 5 requests per second (RPS)
Access Tokens: 2
Compute Units are renewed daily, but unused CUs cannot be transferred to the next day.
Clients who want to increase their usage limits can choose between the higher-tier options.
This is a monthly subscription designed for use cases that are growing beyond the free tier. It offers a significant increase in CU compared to the Free plan.
CU: 50M per month (~1.6M/day)
Rate: 25 requests per second (RPS)
Access Tokens: 10
Additional CU packages can be purchased as needed.
The Pro Plan is the perfect middle ground before going custom. It's built for applications that need higher throughput and increased resource availability.
CU: 600M per month (~20M/day)
Rate: 200 requests per second (RPS)
Access Tokens: 50
Purchase additional CU packages when required
The Enterprise plan is fully customizable with tailored CU allocations, rate limits, and access tokens to meet exceptionally high call volumes and performance requirements.
CU: Custom monthly allocation based on your demands
Rate limit: Custom
Access Tokens: Custom
Additional CU packages can be purchased on demand
If you’re unsure which plan best fits your needs, our team is ready to help! or visit our page for more information.
GetBlock users can top up their CU balance or upgrade to higher limits directly from their Dashboard, with a few click.
The current CU balance for Shared Node users is displayed on the Dashboard. This shows how many Compute Units (CUs) are left before running out.
With the "Top Up" feature, users can add more Compute Units to their account or upgrade to higher monthly limits.
Starter, Pro & Enterprise users can refill their CU balance or switch to another plan for increased limits:
Click the "Top Up" button on the Dashboard.
Select the number of CUs you’d like to add or choose the recommended plan (if prompted) based on your usage needs.
Confirm and finalize your purchase.
Your account balance will be updated immediately upon successful payment.
Free plan users cannot top up their Compute Units directly. Instead, you have the option to upgrade to one of our monthly paid plans, providing significantly higher limits and extra features.
If you're on the Enterprise plan (our customizable Shared Node plan), you can additionally request higher RPS and Access Token limits. Here’s how:
Click "Change" on the Dashboard next to the Rate Limit section.
Fill out and submit a request form, choosing your desired RPS limit, CU amount, and number of Access Tokens.
Our team will review your request and reach out to you with next steps shortly.
This feature is perfect for users who need higher transaction throughput without changing their plan. For more demanding needs, consider .
Learn what Compute Units (CUs) are and how GetBlock calculates them to track and price API calls
In our Shared Node plans, we use CU-based pricing. CUs, Compute Units, is a way to measure the computational resources that each API request consumes.
Requests are the raw number of calls (e.g., an RPC method call) you make to the node, while Compute Units show how much computing power each call uses.
Instead of charging a fixed fee for every call, GetBlock calculates the “cost” of processing a request based on the actual computational work involved – such as CPU & memory usage, and disk I/O.
Here's how it works:
Different shared node plans include different allocations of Compute Units (CUs).
Each API call deducts an amount based on the resources it consumes.
Users can track their remaining CUs in real time on the dashboard.
This model ensures costs are aligned with actual infrastructure usage.
Every API call "spends" a number of Compute Units. The total value is determined by two main factors:
A base CU cost (chain multiplier) reflecting the network's resource intensity.
A method-specific multiplier which varies by API method.
The total Compute Units for an API call are calculated using the following formula:
Not all blockchains are built or operate the same way. GetBlock accounts for inherent differences between networks by assigning chain multipliers based on factors such as:
Node infrastructure costs;
Protocol complexity and the size of the blockchain data;
Operational overhead.
Here’s how blockchains are grouped based on their average resource intensity:
Algorand, Bitcoin, Bitcoin Cash, Dash, Dogecoin, Ethereum Classic, Kusama, Litecoin, Near, OKB, Polkadot, RSK, Scroll, Shiba Inu, Sonic, Syscoin, Telos, Zcash, others
10
These chains typically have low write/read complexity and use fewer resources per request
Aptos, Arbitrum, Avalanche, BNB Smart Chain, Base, Blast, Cardano, Cosmos, Cronos, Ethereum, Filecoin, Flow, Gnosis, Harmony, Kaia, Linea, Moonbeam, OKT, Optimism, Polygon, Polygon zkEVM, StarkNet, Tezos, Tron, XRP, opBNB, zkCronos, zkSync
20
Requests on these blockchains are more resource-intensive
Solana, Sui, TON
50
These chains require significantly more computational resources per request
Different API methods put different loads on backend nodes. For example:
eth_blockNumber
is lightweight since it just returns the latest block number.
trace_replayBlockTransactions
executes a full replay of all txs in a block and can be extremely heavy.
Therefore, individual blockchain methods have their own multipliers, depending on how computationally demanding each particular operation is.
The example table below shows some Ethereum blockchain methods with their associated multipliers and total CU calculated.
eth_blockNumber
1
20
20
eth_getTransactionByHash
1
20
20
debug_traceTransaction
2
20
40
debug_traceBlock
2
20
40
trace_call
2
20
40
trace_transaction
2
20
40
txpool_status
2
20
40
trace_replayTransaction
4
20
80
Calculation example for
debug_traceTransaction
:
Tracking and pricing requests based on how “heavy” they are:
Discourages abuse (like hammering archive calls) and protects node performance & uptime.
Makes it easier for GetBlock to scale and optimize resources behind the scenes.
A simple per-request pricing model would charge the same for all methods, which isn’t scalable or logical. The CU model fixes this imbalance.
Because each API call has a clear CU cost, you can spot inefficiencies quickly (e.g. which parts of your dApp consume the most), making it easier to fine-tune performance.
— Check how many CUs are included in each plan.
For full details on all methods—including exact multipliers and total CU values for each protocol—please refer to our.
Explorer API
Track transactions and monitor network activity with real-time blockchain data
Getting Started
Create your account, explore plans & features, and make your first API call
Guides
Set up endpoints, manage access tokens, and integrate GetBlock APIs step-by-step
API Reference
View supported networks, available endpoints, and full API specifications
Configure and manage blockchain node endpoints through GetBlock, offering easy creation of shared nodes
Set up and manage blockchain node endpoints with GetBlock. This section covers creating shared node endpoints, generating access tokens, and configuring dedicated nodes with customizable settings.
GetBlock uses a secure authentication method based on access tokens to ensure that only authorized users can interact with blockchain nodes.
The <ACCESS_TOKEN> authenticates requests directly through the endpoint URL.
To make a request, include your full endpoint URL with the access token in the path.
For example, here’s how to fetch the latest Ethereum block number:
Response:
Always store your access tokens securely. Avoid exposing them in publicly accessible code repositories or logs.
If a token is compromised, you can quickly roll or delete it without disrupting other endpoints:
Go to your GetBlock Dashboard.
Locate the endpoint associated with the token.
Select the option to either roll (regenerate) or delete the token.
This authentication method ensures that all your interactions with GetBlock’s services remain secure, reliable, and easy to manage.
Track and extend your dedicated node subscriptions on GetBlock.
This page explains how to manage your dedicated node subscriptions, including checking their status and extending the service duration—all from your user account.
GetBlock is introducing an advanced Dedicated Node service with updated pricing:
Existing users can extend their subscriptions at the old pricing until May 1, 2025.
New users can purchase new subscriptions at the current pricing until the service upgrade begins on March 25, 2025.
You can monitor the status of your dedicated node subscriptions in three different ways.
The widget on your dashboard alerts you when your subscription is about to expire or is in a grace period. Click the widget to open a pop-up that lists all nodes that require renewal.
The Manage Plans section can be found by navigating to the “Pricing” option in the left-side menu. You'll see three tabs: click on “Manage Plans” to view all your subscriptions in one place.
Each endpoint in “My endpoints” list now shows its current subscription status.
)
)
(One-Time Payment)
(Recurring /One-Time)
You can modify your subscription period at any time if you’re on a one-time payment plan paid with:
Cryptocurrency;
Credit card.
Users cannot manually extend a plan when using recurring payments. These subscriptions renew automatically at the end of a billing cycle.
However, if a payment fails (e.g., due to an expired card or insufficient funds), your subscription will enter a 3-day grace period. During this time, your node remains active, allowing you to update your payment details and retry the renewal before the service is interrupted.
You can extend your subscription to one of the following periods:
1 month
6 months
12 months
There are three ways to extend your subscription.
Go to Dedicated Nodes tab from your dashboard. Look for the subscription alert widget.
Click the widget to see a list of nodes needing renewal and choose one. A pop-up will show extension options (1, 6, or 12 months).
Choose a new period and review details. Proceed to checkout.
Complete the payment by following the instructions provided.
Check the "Payment History" under the Pricing tab to track the progress.
For fiat (credit card) payments:
Payments are processed via Paddle.
VAT may apply depending on the user's location.
The extension is applied instantly once the payment is completed.
For crypto payments:
Payments are processed via NOWPayments.
Make sure to account for network fees to avoid payment issues.
The extension is applied after blockchain confirmation, which may take a few minutes.
Navigate to your main dashboard and switch to the Dedicated Nodes tab.
Choose a node to extend. Expand the node’s details and click "Extend" to begin the process.
Follow the pop-up instructions to select the new subscription period and finalize the process.
Navigate to Pricing > Manage Plans.
Review all subscriptions. Subscriptions nearing expiration are listed at the top.
Follow the same steps: Select your node, choose a new period, and confirm your payment.
If you face any issues with renewal or extensions, feel free to reach out to GetBlock support—we’re happy to assist.
Track and manage your usage and node service subscriptions with GetBlock.
These tools help ensure optimal use of GetBlock’s services and keep you informed of key metrics and events related to your account.
The Dashboard provides a quick snapshot of key metrics:
Your current plan details
Remaining CU balance
Rate limit based on your plan
Total requests made in the last 24 hours
For more detailed analysis, visit the Statistics tab in ‘My Endpoints’ section.
Select the time period, protocol name, networks (mainnet/testnet), and API interfaces to analyze the data by parameters.
All data is displayed through infographics, including:
Number of requests
Response statuses
Method call distribution
Rate limit rejections
GetBlock provides a notification system to help you monitor your usage and subscription status.
Alert types:
Run out of CU: Notifies you when your CU balance reaches zero.
CU balance alerts: Warns when remaining CUs drop below specified limits.
Subscription expiration alerts: Help you renew your dedicated node plans on time.
Set up email, Telegram, or Webhook alerts to monitor your usage and subscription status from Settings → Notification Settings.
Set up your team account on GetBlock, invite and onboard team members with this step-by-step guide.
A team account is a shared workspace where multiple users can collaborate. This setup is ideal for companies and teams using GetBlock services.
Key benefits:
Organized collaboration: Work together on company resources.
Enhanced security: Role-based access limits each member to only the features they need.
Efficient management: Easily switch between personal and team accounts.
A team account user is a regular GetBlock user. When invited to a team, they can work on company resources, manage service plans or team settings—provided the corresponding permissions are granted.
This part covers a step-by-step guide to setting up your team workspace.
Click on the profile icon in the bottom-left corner of the sidebar. Select "Create new team" from the dropdown menu.
A popup window will appear. Assign a team name and click the "Create team" button.
Once the space is created, navigate to Account Settings > Team to manage team settings or add teammates.
The creator of the team account controls who gets invited and manages user roles.
Limits on GetBlock team accounts:
Each user can create up to 3 teams.
A user can be invited to an unlimited number of teams.
One team can have a maximum of 30 users.
You can invite team members to join your team account using either their email address or GetBlock User ID.
If the teammate has a GetBlock account: You can invite them using their ID. Since they are already registered, they just need to accept the invitation.
If the teammate is not registered on GetBlock: Invite them via email so they can first create an account before joining the team.
Go to Account Settings > Team.
Click "Add team member" in the top-right corner.
Request the User ID from the teammate (they can find it under Account Settings > General).
Enter the name, User ID, and send the invite.
The user gets a notification and can accept the invite.
Go to Account Settings > My Team.
Click "Add team member" in the top-right corner.
Enter the teammate's name and email address.
Send the invite.
The invite link is valid for 30 minutes. If it expires, please resend an invitation.
The user will receive an invitation email with a link to sign up and join the team.
Once the user has joined, the team owner or an admin can update their permissions:
Go to My Team in Account Settings.
Click the three-dot menu (⋮) next to a team member.
Select "Edit access level".
Assign permissions:
Endpoints: Create and manage node endpoints, access tokens, and view statistics.
Subscriptions & payments: Handle payments and plans.
Admin: Includes all the above permissions, plus the access to manage team settings and member roles.
Save changes.
If a Member has no permissions assigned, they will have View-Only access by default.
This table provides a breakdown of actions team account users can perform based on their role.
If you need someone to help manage other team members, be sure to give them Admin status.
To remove a user from your team account:
Navigate to Team in the Account Settings.
Click the three-dot menu (⋮) next to the team member name.
Select "Remove" from the dropdown menu.
When removed from a team, users lose access to that team workspace but keep their personal account.
If you’ve been invited to a team on GetBlock, follow these steps to accept the invitation and join the team.
Click your account icon to view an invitation.
Click "Accept" if you're ready to join.
When someone who is not yet registered on GetBlock receives a team invitation, they must first sign up for an account:
Check your inbox for an email invitation from GetBlock.
Clicking the invitation link redirects you to the sign-up page.
Create a secure password for your new account.
Check the boxes to agree to the Terms of Service and Privacy Policy and complete the registration.
The invite link is valid for 30 minutes. If it expires, ask the team owner or admin to send a new invitation.
A team user does not lose access to their personal account. They can still use and manage their own endpoints and subscriptions.
To switch between your personal account and any team accounts you are part of:
Click the account icon in the left panel.
A dropdown will show all teams & personal accounts.
Switch between them as needed.
The teams list is sorted by recent activity, with the most recently accessed accounts at the top.
Regularly review and audit permissions. Revoke access for users who are no longer active.
Grant admin privileges only to trusted team members.
Give Members only the necessary permissions (e.g., endpoints access or subscriptions management).
Never share login credentials—use team accounts instead.
Follow the steps below to set up an endpoint and generate access tokens for your project.
Log in to your GetBlock account and navigate to the Dashboard.
Scroll down to find the My Endpoints section on the Dashboard.
Choose the desired blockchain protocol (e.g., Ethereum, BNB Chain, Polygon).
Select the specific network you want to interact with (mainnet or testnet).
Pick the API method that you need (e.g., JSON-RPC, WebSockets, GraphQL, etc).
Click 'Get' and have the endpoint URL with an access token generated.
To see all the access tokens generated for a specific protocol, simply expand the endpoint.
Each protocol has a configuration file that includes all relevant access token details.
The All Access Tokens Configuration file is located next to the My Endpoints section. Use it to review and manage your tokens.
Every you create is assigned a unique access token:
Click the three-dot icon () next to the endpoint.
Sign in to your GetBlock account. If you don’t have a user account yet, create one following .
A team member is marked as when they have successfully accepted the invitation and joined the team.
If the invitation has been sent but not yet accepted, their status remains .
When you have a pending team invitation, a notification badge appears on your account icon .
After accepting the invitation, you are given access to your team’s workspace. Your will be determined by the team owner or admin.
Once registered, you’ll have your personal GetBlock account. Additionally, you gain access to the team’s dashboard and resources based on given by the team owner or admin.
– Learn more about GetBlock.
– How to create and manage node endpoints.
– Understanding plans and payments.
If you run into any issues or have questions, please check out our or visit our . You can also use the Help button within your GetBlock dashboard to access support or submit a request.
Generate and add as many as required for this protocol. Each token is a unique endpoint for you and your application to interact with the blockchain.
Create & manage access tokens
✅
✅
Manage subscriptions & payments
✅
✅
Add & remove team members
✅
✅
❌
Edit access levels
✅
✅
❌
Promote to Admin
✅
❌
❌
This section provides simple examples to help you test your connection to the blockchain, using Ethereum API as a reference.
Learn how to interact with blockchain networks through GetBlock’s node infrastructure using popular web3 libraries.
Here you'll find step-by-step instructions on how to integrate popular developer libraries like Web3.js, Ethers.js, and others with GetBlock API.
These libraries allow developers to interact with Ethereum and other EVM-compatible blockchains to read data, send transactions, and deploy smart contracts.
The guide covers setting up your connection to GetBlock and performing basic operations.
These examples provide a starting point for testing your connection and querying blockchain data using cURL commands.
Before you start:
Create a JSON-RPC endpoint for the Ethereum blockchain from your GetBlock account.
Replace <ACCESS_TOKEN> in the examples below with your actual Access Token.
Run the following command to retrieve the latest block number:
If successful, the response will include the current block number in hexadecimal value:
Identify the blockchain network with the eth_chainId
method:
Response example:
In this example, 0x1
indicates the Ethereum Mainnet. The chain ID helps confirm which blockchain network you are interacting with.
Retrieve the balance of an Ethereum address using eth_getBalance
. Replace <ACCOUNT_ADDRESS>
with the target wallet address:
Example response:
The result field shows the account balance in wei (1 ether = 10¹⁸ wei).
GetBlock supports both fiat and crypto payments.
Users can pay for subscriptions using traditional fiat currency via Paddle.
How it works:
Recurring payments enabled by default: Payment is automatically deducted on the billing date.
Fees: VAT is applied to Paddle payments and varies depending on your region
If the card balance is insufficient: GetBlock will retry the payment after three days. If the retry fails, the plan will be frozen until the payment is resolved.
Please, account for VAT when planning your payments.
To update your payment information while you have an active subscription:
Go to Pricing → Manage Plans.
Click ‘Edit Payment Method’.
Enter your updated payment details and save the changes.
Users can top up their accounts with cryptocurrency through NOWPayments.
How it works:
Payments are processed as one-time transactions: add funds as needed.
Supported cryptocurrencies: any token on any network available through NOWPayments at the time of payment.
Fees: blockchain network fees apply.
If the network fees are insufficient or the transaction fails, the payment will not be processed and the subscription plan will not be activated. Please, include enough gas fees to ensure the transaction processes successfully.
Configure dedicated nodes in your GetBlock Dashboard. This guide covers customizing your node settings and completing the setup process.
Select a blockchain protocol you wish to deploy and the network type. Click Get to begin the setup process. In the setup window:
Review and confirm your selected protocol and network.
Select a subscription plan (available discounts are applied automatically).
Customize your dedicated node with the following options:
Node type: Choose between Full Node or Archive Node.
Node client: Specify your preferred node implementation.
API Interface: Select API options.
Verify all selected configurations in the summary section and proceed to checkout.
Pay for your dedicated nodes via your GetBlock account. If additional support is required during setup, you can contact the GetBlock support team directly.
You can add more dedicated nodes following these steps. Add as many access tokens for each dedicated node as you need.
Learn how to use Web3.js, a widely-used JavaScript library for connecting to GetBlock nodes.
Web3.js is a JavaScript library built for interacting with the Ethereum blockchain and other EVM-compatible chains. It is used to send JSON-RPC calls to the Ethereum node via HTTP, IPC, or WebSocket connection to read data from the blockchain, make transactions, or deploy smart contracts.
Use your preferred package manager:
npm:
yarn:
Pure js link:
For a list of supported RPC methods with examples, navigate to .
To create a endpoint, switch over to the ‘Dedicated Nodes’ tab in the Dashboard.
For additional methods and options, refer to the official .
Download the Postman GetBlock’s collection to test our service. It includes all the accessible endpoints of our nodes and ready-to-go examples.
Once the page loads, you'll find a 'Run in Postman' button in the top-right corner. Click this button to open the collection directly in your Postman application.
Select the desired network from the drop-down list on the sidebar.
Paste the access token copied from your account instead of {YOUR_ACCESS_TOKEN}
.
This token will grant you the necessary permissions to explore our node functionalities.
This page provides a guide to common JSON-RPC and HTTP errors when testing your connection with GetBlock's API.
401
Access denied
Double-check that <ACCESS_TOKEN>
is correctly replaced with your actual token. Ensure there are no trailing spaces.
404
Could not resolve host
Verify that the URL https://go.getblock.io/<ACCESS_TOKEN>/
is correct.
429
Too many requests
Check your GetBlock account for usage limits. Upgrade your plan if necessary.
GetBlock’s configuration file provides a more organized and flexible way to interact with blockchain nodes and networks without exposing sensitive API keys or credentials in the code.
Using GetBlock’s JSON configuration file with curl is particularly helpful when you need to access various node endpoints without hardcoding API keys in the code:
Download the getblock.config.json
file from your GetBlock account;
Navigate to your workspace or directory where you have imported the getblock.config.json
file and open a terminal;
Now, you can make a GET request to a selected node endpoint using the curl command:
Connect to Ethereum nodes and other EVM-compatible networks using web3.js and GetBlock’s JS configuration file.
Make sure the web3.js library is added to your project. In order to do that, use one of the following methods:
Npm: npm install web3
Yarn: yarn add web3
Pure js link: dist/web3.min.js
Download the getblock.config.js
file from your GetBlock account. Add this file to your project directory.
Import the getblock
module to a .js file that configures a new Web3 instance:
Connect to an Ethereum node and start sending API calls using web3.js over HTTP or WebSocket in the format below:
Use go()
method to access an entire endpoint or token()
to fetch the token.
Set up GetBlock’s JS config file in Hardhat following the steps below:
Ensure you have Hardhat installed as a dependency in your Node.js project or run the following command to do so:
Navigate to your GetBlock account and install the getblock.config.js
file. Copy and paste it into your working directory;
Open the hardhat.config.js
file from your project directory and import the getblock
module:
To set up GetBlock as a provider, modify the Hardhat configuration file with the credentials as shown below. Use go()
method to access an entire endpoint or token()
to fetch the token only.
In this guide, we will show you how to get started with TronWeb to connect to GetBlock.
TronWeb is a JavaScript library of TRON full node’s API functions that is used to deploy smart contracts, query blockchain and contract information, trade on the decentralized exchanges and change the blockchain state.
Firstly, you will need to add the TronWeb library to your project.
Npm:
Yarn:
In your javascript file, define TronWeb:
When you instantiate TronWeb you can define:
fullNode
solidityNode
eventServer
privateKey
you can also set a
fullHost
Which works as a jolly. If you do so, though, the more precise specification has priority. Supposing you are using a server which provides everything, like TronGrid, you can instantiate TronWeb as:
For retro-compatibility, though, you can continue to use the old approach, where any parameter is passed separately (using the GetBlock node as an example here):
After this you can call any TronWeb method:
To get started, follow these steps:
Sign up: Create an account to access your Access Token.
Generate access token: Navigate to the dashboard, and generate your first access token for API authentication.
Choose the blockchain name and type: Select the blockchain network you want to interact with, set up testnet/mainnet, and choose the interface you’re going to use.
Send your first request:
GetBlock is offering one of the most comprehensive APIs toolkits in the segment supporting hundreds of dApps with fast and reliable connection to blockchain nodes.
Seamless connection to full and archive nodes
Shared and dedicated nodes: Tailored for your dApp’s needs.
Programmable and non-programmable blockchains
L1 and L2 protocols
EVM and non-EVM networks
WebSockets
JSON RPC
GraphQL
REST API
And more to come
DAS API
Firehose
Blockbook
Yellowstone Geyser
Most *nix-based systems come with cURL pre-installed. cURL is a command-line tool and library for transferring data with URLs. To check if cURL is installed, run the following command:
Example of requesting the latest block number using the GetBlock API and cURL:
To run Python examples, ensure Python is installed along with the requests package. You can install the package using the following command:
Example:
For JavaScript examples, you'll need Node.js version 18 or later. Follow the official documentation to install the latest stable version globally. Verify your installation by running:
To execute Ruby examples, install Ruby on your machine. Refer to the official installation guide for details. Confirm installation by running:
We provide APIs for a wide range of networks, including:
Set up GetBlock as a provider using Ethers.js library to interact with the blockchain and streamline your dApp development process.
Ethers.js is a lightweight JavaScript library for interacting with Ethereum and other EVM-compatible blockchains. It is commonly used by developers to build decentralized applications (dApps) and manage Ethereum-based operations like deploying smart contracts, interacting with them, and managing user wallets.
Add Ethers.js to your project using your preferred package manager:
npm
yarn
Import the collection into your Postman workspace: .
32601
The method does not exist/is not available
Verify the method name (eth_blockNumber
, eth_getBalance
, etc.) against the blockchain's JSON-RPC .
32602
Invalid argument
Ensure the parameters in the params
array match the expected format for the method.
32700
Parse error
Double-check your JSON syntax. Ensure your request is properly formatted.
Make sure you have installed. jq is a versatile command-line tool that enables extracting values from JSON files;
All API references can be found in the project documentation at
See full list: All mainstream RPC interfaces
Add them in Lego-like manner:
Need more? Don’t hesitate to contact sales:
For further details and advanced usage, explore the .
Learn how to set up custom RPC URL on MetaMask for faster, more reliable, and secure blockchain interactions.
MetaMask is a blockchain wallet available as a mobile application and a browser extension. It allows you to interact with Ethereum-based decentralized applications (dApps) directly from your browser.
Using GetBlock nodes with MetaMask makes your blockchain experience faster and more reliable than using default RPCs:
Connect directly to trusted nodes for secure transactions.
Enjoy quicker transactions and smoother dApp interactions.
Experience less downtime, even during busy network periods
This step-by-step tutorial will guide you through connecting GetBlock’s powerful nodes to your MetaMask wallet.
MetaMask extension is officially supported on Chrome, Brave, Firefox, Microsoft Edge, and Opera browsers.
If the network is already in your list but uses a default RPC provider, you can switch to GetBlock by following these steps:
Click on the current network name in MetaMask to open the dropdown of networks.
Open the ‘Default RPC URL’ dropdown and select 'Add RPC URL'.
Paste the JSON-RPC endpoint URL from your GetBlock account (https://go.getblock.io/<ACCESS_TOKEN>/
).
Name the new RPC URL for easier identification.
Click 'Add URL', then 'Save' to confirm.
You can now switch between RPC URLs for that network as needed.
If the network isn’t in your list, you can add it as a custom network. For this example, we will add the Polygon zkEVM to MetaMask.
Click on the current network name.
Select 'Add a custom network'.
Fill in the required fields:
RPC URL
The network's JSON-RPC URL from your GetBlock account
https://go.getblock.io/<ACCESS_TOKEN>/
Chain ID
The ID of the network
1101
Network name
Fetched automatically based on Chain ID
Polygon zkEVM
Currency symbol
Suggested automatically based on Chain ID
ETH
Block explorer URL
Optional field
https://zkevm.polygonscan.com/
Click 'Save', and the custom network will be added and selected as default.
This guide explains how GetBlock users can connect to blockchain nodes to create accounts and send transactions.
In blockchains, ‘account’ should be referred to as a pair of private and public keys. Blockchains ‘recognize’ their users and balances by these keypairs.
Unlike login/password pairs in traditional computational solutions, in modern blockchains, every account can be restored with a private key only.
So, to broadcast transactions to a decentralized network, we need first to create (or restore) our account. The whole set of interactions is organized via Web3.js library.
First, initialize the Web3.js library and set up the connection to a blockchain node:
We can also restore an account from an existing private key:
You may ask what does ‘eth’ mean when we’re interacting with BNB Chain? No mistake, it reflects the fact that BNB Smart Chain is fully compatible with Ethereum Virtual Machine.
In blockchains, transactions should be signed (authorized) to be ‘included’ into blockchains (confirmed by its consensus of miners or validators).
Here’s how our transactions are created. 0.01 ETH is used for demo.
That’s how the transaction looks before being included in the blockchain. Once signed, it can be sent to the network of nodes.
That’s it: your account is good to go and its transaction is submitted successfully!
Example code for the /v1/accounts/{account_hash}/modules json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/modules json-rpc in GetBlock.io Web3 documentation.
limit
-
Maximum number of resources to retrieve. Gets default page size if not provided.
ledger_version
-
Ledger version. Defaults to latest if not provided.
start
-
Optional cursor specifying pagination start. You can call this endpoint once without this parameter, and then use the cursor returned in the X-Aptos-Cursor header in the response.
If you don’t already have MetaMask, download and install it from the official website: .
Generate a JSON-RPC URL for the selected network from your GetBlock and copy it.
Find the network you want to edit and click the settings menunext to it. Select 'Edit'.
Next, we can create an account on the testnet:
Example code for the /v1/accounts/{account_hash}/module/{module_name} json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/module/{module_name} json-rpc in GetBlock.io Web3 docume
Example code for the /v1/accounts/{account_hash}/events/{event_handle}/{field_name} json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/events/{event_handle}/{field_name} json-rp
Example code for the /v1/accounts/{account_hash}/events/{creation_number} json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/events/{creation_number} json-rpc in GetBlock.io Web
Example code for the /v1/accounts/{account_hash}/resource/{resource_type} json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/resource/{resource_type} json-rpc in GetBlock.io Web
Example code for the /v1/accounts/{account_hash}/resources json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/resources json-rpc in GetBlock.io Web3 documentation.
limit
-
Maximum number of resources to retrieve. Gets default page size if not provided.
ledger_version
-
Ledger version. Defaults to latest if not provided.
start
-
Optional cursor specifying pagination start. You can call this endpoint once without this parameter, and then use the cursor returned in the X-Aptos-Cursor header in the response.
Example code for the /v1/accounts/{account_hash}/transactions json-rpc method. Сomplete guide on how to use /v1/accounts/{account_hash}/transactions json-rpc in GetBlock.io Web3 documentation.
Example code for the /v1/blocks/by_version/{version} json-rpc method. Сomplete guide on how to use /v1/blocks/by_version/{version} json-rpc in GetBlock.io Web3 documentation.
Example code for the /v1/transactions json-rpc method. Сomplete guide on how to use /v1/transactions json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_call json-rpc method. Сomplete guide on how to use eth_call json-rpc in GetBlock.io Web3 documentation.
object
- json object
The transacion call object in format: { "from": "address" (optional, string) - The address the transaction is sent from. "to": "address" (optional, string) - The address the transaction is directed to. "gas": "quantity" (optional, string) - Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions. "gasPrice": "quantity" (optional, string) - Integer of the gasPrice used for each paid gas "value": "quantity" (optional, string) - Integer of the value sent with this transaction "data": "data" (optional, string) - Hash of the method signature and encoded parameters. }
QUANTITY|TAG
- string
integer block number, or the string "latest", "earliest" or "pending".
Example code for the /v1/blocks/by_height/{block_height} json-rpc method. Сomplete guide on how to use /v1/blocks/by_height/{block_height} json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getBalance json-rpc method. Сomplete guide on how to use eth_getBalance json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getBlockByHash json-rpc method. Сomplete guide on how to use eth_getBlockByHash json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_estimateGas json-rpc method. Сomplete guide on how to use eth_estimateGas json-rpc in GetBlock.io Web3 documentation.
object
- json object
The transacion call object in format: { "from": "address" (optional, string) - The address the transaction is sent from. "to": "address" (optional, string) - The address the transaction is directed to. "gas": "quantity" (optional, string) - Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions. "gasPrice": "quantity" (optional, string) - Integer of the gasPrice used for each paid gas "value": "quantity" (optional, string) - Integer of the value sent with this transaction "data": "data" (optional, string) - Hash of the method signature and encoded parameters. }
QUANTITY|TAG
- string
Optional.
integer block number, or the string "latest", "earliest" or "pending".
Example code for the eth_getStorageAt json-rpc method. Сomplete guide on how to use eth_getStorageAt json-rpc in GetBlock.io Web3 documentation.
Example code for the db_putString {disallowed} json-rpc method. Сomplete guide on how to use db_putString {disallowed} json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getBlockByNumber json-rpc method. Сomplete guide on how to use eth_getBlockByNumber json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getBlockTransactionCountByNumber json-rpc method. Сomplete guide on how to use eth_getBlockTransactionCountByNumber json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getTransactionByBlockNumberAndIndex json-rpc method. Сomplete guide on how to use eth_getTransactionByBlockNumberAndIndex json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getTransactionCount json-rpc method. Сomplete guide on how to use eth_getTransactionCount json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getUncleByBlockHashAndIndex json-rpc method. Сomplete guide on how to use eth_getUncleByBlockHashAndIndex json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getUncleByBlockNumberAndIndex json-rpc method. Сomplete guide on how to use eth_getUncleByBlockNumberAndIndex json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getUncleCountByBlockNumber json-rpc method. Сomplete guide on how to use eth_getUncleCountByBlockNumber json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_getTransactionByBlockHashAndIndex json-rpc method. Сomplete guide on how to use eth_getTransactionByBlockHashAndIndex json-rpc in GetBlock.io Web3 documentation.
Example code for the eth_sendTransaction json-rpc method. Сomplete guide on how to use eth_sendTransaction json-rpc in GetBlock.io Web3 documentation.
object
- json object
The transacion call object in format: { "from": "address" (optional, string) - The address the transaction is sent from. "to": "address" (optional, string) - The address the transaction is directed to. "gas": "quantity" (optional, string) - Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions. "gasPrice": "quantity" (optional, string) - Integer of the gasPrice used for each paid gas "value": "quantity" (optional, string) - Integer of the value sent with this transaction "data": "data" (optional, string) - Hash of the method signature and encoded parameters. "nonce": "quantity" (optional, string) - Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce. }
Example code for the eth_signTransaction json-rpc method. Сomplete guide on how to use eth_signTransaction json-rpc in GetBlock.io Web3 documentation.
object
- json object
The transacion call object in format: { "from": "address" (optional, string) - The address the transaction is sent from. "to": "address" (optional, string) - The address the transaction is directed to. "gas": "quantity" (optional, string) - Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions. "gasPrice": "quantity" (optional, string) - Integer of the gasPrice used for each paid gas "value": "quantity" (optional, string) - Integer of the value sent with this transaction "data": "data" (optional, string) - Hash of the method signature and encoded parameters. "nonce": "quantity" (optional, string) - Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce. }
Example code for the eth_subscribe json-rpc method. Сomplete guide on how to use eth_subscribe json-rpc in GetBlock.io Web3 documentation.
type
- string
A subscription type, such as newHeads
(new headers appended to the chain, including chain reorganizations), logs
(logs that are included in new imported blocks and match the given filter criteria) or newPendingTransactions
(hashes for all transactions that are added to the pending state and are signed with a key that is available in the node).
objects
- hex string
Optional arguments such as an address, multiple addresses, and topics.
Example code for the shh_newFilter {disallowed} json-rpc method. Сomplete guide on how to use shh_newFilter {disallowed} json-rpc in GetBlock.io Web3 documentation.
filters
- json object
filter object: { "to": "address" (string, optional) - Identity of the receiver. When present it will try to decrypt any incoming message if the client holds the private key to this identity. "topics": ["topic"] (array of string) - Array of topics which the incoming message’s topics should match. }