Base RPC
The QuickNode Base documentation constantly evolves as the chain undergoes upgrades and changes. We highly recommend cross-referencing with the Base Documentation for the latest updates.
Overview
At QuickNode, we are currently running Base Mainnet and Testnet RPC endpoints. In aggregate, we serve hundreds of billions of requests every month. To make it easier for developers to integrate with QuickNode, we've created this documentation that shows how to call RPC methods using cURL, JavaScript, Python, Ruby and any applicable Web3 SDKs. QuickNode-supported Base API include:
- Ethereum JSON-RPC API
- Debug API
- Trace API
- OP-Node JSON-RPC API
- Marketplace Add-Ons
- Base Blockbook JSON-RPC
- Block Timestamp Lookup
- Single Flight
Base Network Support
| Network | WSS | HTTPS |
|---|---|---|
| MAINNET | ✅ | ✅ |
| SEPOLIA | ✅ | ✅ |
Making Base API Requests
In this documentation, you will see example requests made with various programming languages and Web3 SDKs for each supported Base method. This section will explain how to execute each one of them on your machine.
QuickNode SDK
To run the QuickNode SDK code examples, you'll need to have the QuickNode SDK installed. You can find out more about the QuickNode SDK at the getting started page. If you'd like to use it, please be sure to install it like so:
npm install @quicknode/sdk
cURL
Most *nix based systems have cURL support out of the box. cURL is a command line tool and library for transferring data with URLs. Check if you have it by running the following:
curl -h
Python
To run our Python code examples, you'll need to have Python installed as well as the requests package. You can install this package with the following command:
python -m pip install requests
JavaScript
To run our JavaScript code examples, you'll need to have Node v18 and up installed. You can follow this official document to install the latest, stable version of Node globally. Check if you have it by running the following:
node -v
Ruby
To run our Ruby code examples, you'll need to have Ruby installed. You can follow this official installation document for more information. Check if you have it by running the following:
ruby -v
Web3.py
Web3.py is a Python library for interacting with Ethereum. If you'd like to use it, please be sure to install it like so:
pip install web3
Ethers.js
At QuickNode we prefer ethers.js as our JS library for interacting with JSON-RPCs when possible. Ethers aims to be a complete and compact library for interacting with the Ethereum Blockchain and its ecosystem. If you'd like to use it, please be sure to install it like so:
npm install --save ethers
Web3.js
There is also Web3.js - it's a collection of libraries that allow you to interact with a local or remote ethereum node using HTTP, IPC or WebSocket. If you'd like to use it, please be sure to install it like so:
npm install web3
Eth.rb
Eth.rb is a comprehensive ruby library that provides a high-level interface to interact with the Ethereum blockchain, making it easier for developers to manage accounts, send transactions, and work with smart contracts. If you'd like to use it, please be sure to install it like so:
gem install eth
API Credits
Usage in our pricing plans is measured in API Credits. To learn more about the API Credits for Base, please visit this page.
WebSocket Limits
WebSocket responses are capped at a certain limit, which is subject to change. In cases where responses are potentially large, it is recommended to use a POST request. If the response size exceeds the limit, the associated error code will be -32616.
Endpoint Authentication Options
Please note that setting JWT (JSON Web Tokens), configuring all whitelist options, and changing any rate limits beyond credits per second are only available to users on the Build plan and higher. Users on the Free plan can only change their requests per second rate limit or add, use, and delete an authentication token. Visit our pricing page for more information.
Token Authentication
By default, all endpoints created on QuickNode are protected by a token in the URL which looks something like this:
http://sample-endpoint-name.network.quiknode.pro/token-goes-here/Approved Referrer List
For endpoints on the shared network, you are able to add a list of approved referrers. This requires any HTTP request to send a REFERRER header or any WebSocket request to send an ORIGIN header populated with one of the referrers you entered into our user panel.
Disabling Token Authentication
You can also disable the token authentication completely in your security settings for a given endpoint. This will allow anyone to make requests to the endpoint without the token.
JWT (JSON Web Tokens)
For additional security, you can also enable JWT for each of your deployed endpoints. JWT allows for stateless authentication between you and your endpoint. Learn how to use JWT with QuickNode in this step-by-step guide.
Multiple Authentication Tokens
Create multiple authentication tokens for each of your deployed endpoints. This allows you to revoke any tokens that may be comprised, without needing to restart your non-compromised endpoint.
To roll an individual authentication token, create an additional token and then delete the previous token. Learn more about multiple authentication tokens in this QuickNode guide.
Secure Your QuickNode Base Endpoint
Enhance the security of your QuickNode RPC endpoints using the Endpoint Armor add-on. This add-on provides a secure URL for safer public and front-end usage, allowing you to control access, set rate limits, and restrict methods for heightened security and streamlined management. You can find more information about Endpoint Armor on this page.
We ❤️ Feedback!
If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!