Blockchain Intelligence APIs: GET Node Updates
Blockchain Intelligence APIs: GET Node Updates
This endpoint allows you to query our node update intelligence for a specific chain, network (mainnet/testnet) and get the latest updates for that specific chain. Find the list of supported chains in the chain parameter below. You will need your API key to send requests. If you have any questions or feedback, please reach out to us at support@scale3labs.com.
GET
Blockchain Intelligence APIs: GET Node Updates
Using Query Parameters with GET Node Updates
To enhance your experience with our ‘GET Node Updates’ endpoint, you can use various query parameters provided by the api-query-params library. These parameters allow for advanced filtering, sorting, and pagination, helping you tailor the response to your specific needs. Below are examples demonstrating how to effectively utilize these features.Examples of Query Parameters
- Filtering by Chain and Category with Sorting:
Fetch updates for Ethereum mainnet in the, sorted by the release date and priority.
- Pagination and Selective Fields::
Retrieve the second page of updates, showing 10 records per page, displaying only name, version, and release date.
string
Name of the node update
string
Node update category
string
required
Node update chain. Supported chains include: ( “aptos”,
“arb”,
“atom”,
“avax”,
“base”,
“celo”,
“dot”,
“eth”,
“flow”,
“harmony”,
“kava”,
“mina”,
“near”,
“op”,
“polygon”,
“sei”,
“sol”,
“stx”,
“sui”,
“vet”,
“xlm”)
string
Node update description
string
Name of repository that contains the update code
string
Node update tag. The Tag contains the update version
string
Node update network (mainnet, testnet, devnet)
string
Node update client depending on the chain. For chains with no client the default value is the chain itself. Supported clients include: (
“aptos”,
“atom”,
“avalanchego”,
“base”,
“besu”,
“bor”,
“celo”,
“flow”,
“gaia”,
“geth”,
“harmony”,
“heimdall”,
“horizon”,
“jito”,
“kava”,
“lighthouse”,
“lodestar”,
“mina”,
“near”,
“nethermind”,
“nimbus”,
“nitro”,
“optimism”,
“polkadot”,
“polygon”,
“rocketpool”,
“sei”,
“solana”,
“stacks”,
“sui”,
“teku”,
“thor”)
integer
Release date of the update (unix epoch timestamp)
string
Link to GitHub repository release notes
string
Version of the node update
string
Commit hash of the node update
string
Priority level of the node update
array
Array of prerequisites for the node update
boolean
Boolean indicating if the update has breaking changes
string
Summary of the breaking changes
string
Information about any upcoming network upgrades
boolean
Boolean indicating if the update is required for an upcoming network upgrade
integer
Size of a single page i.e how many records to send back in the response
integer
Page number
200 (OK) Response Object Schema
200 (OK) Response Object Schema
NodeUpdate[]
string
Version of the node update
string
Commit hash of the node update
string
Priority level of the node update
array
Array of prerequisites for the node update
boolean
Boolean indicating if the update has breaking changes
string
Summary of the breaking changes
string
Information about any upcoming network upgrades
boolean
Boolean indicating if the update is required for an upcoming network upgrade
Metadata
required
APIError Response Object Schema
APIError Response Object Schema
ApiError