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.
Network feed chain. Currently supported chains values are (“aptos”,
“algo”, “aptos”, “arb”, “avax”, “base”, “bnb”, “link”, “btc”, “bch”, “ada”, “tia”, “celo”, “atom”, “cro”, “dash”, “doge”, “eos”, “eth”, “etc”, “ftm”, “fil”, “flr”, “flow”, “harmony”, “hbar”, “hnt”, “icp”, “inj”, “kava”, “ksm”, “ltc”, “mina”, “near”, “op”, “dot”, “polygon”, “xrp”, “sei”, “sol”, “stx”, “xlm”, “sui”, “xtz”, “trx”, “ton”, “vet”, “zec”)
Node update client depending on the chain. For chains with no client the default value is the chain itself. Supported clients include: (
“cardanonode”,
“goalgorand”,
“aptos”,
“nitro”,
“avalanchego”,
“base”,
“besu”,
“bsc”,
“bitcoincore”,
“bchd”,
“bitcoincashnode”,
“bor”,
“celestia”,
“celo”,
“chainlink”,
“gaia”,
“cronos”,
“dashd”,
“dogecoincore”,
“eos”,
“erigon”,
“coregeth”,
“goopera”,
“fireeth”,
“flow”,
“forest”,
“geth”,
“goflare”,
“gosongbird”,
“harmony”,
“hedera”,
“heimdall”,
“horizon”,
“icp”,
“injectived”,
“jito”,
“kava”,
“kusama”,
“lighthouse”,
“lighthouse_vc”,
“lighthouse_bc”,
“litecoincore”,
“lodestar”,
“lotus”,
“mina”,
“nethermind”,
“nearcore”,
“nimbus”,
“op”,
“optimism”,
“polkadot”,
“prysm”,
“reth”,
“rippled”,
“rocketpool”,
“sei”,
“solana”,
“stacks”,
“stellarcore”,
“teku”,
“tezos”,
“javatron”,
“ton”,
“testclient”,
“thor”,
“zcashd”)
200 (OK) Response Object Schema
200 (OK) Response Object Schema