Utilizing Query Parameters with GET Network Feed
Similar to our ‘GET Node Updates’ endpoint, the ‘GET Network Feed’ also supports various query parameters for advanced search capabilities. For a detailed guide on using query parameters, please refer to the GET Node Updates documentation. Below are specific examples tailored for the ‘GET Network Feed’ endpoint.Examples of Query Parameters for Network Feed
- Filtering by Label and Chain:
Retrieve network feeds tagged as ‘announcement’ for the ‘Ethereum’ chain.
- Pagination and Network Specific Feed:
Get the second page of feeds for the ‘mainnet’ network, showing 5 records per page.
string
Type of feed. This can be one of: “announcement”, “general information”, “time sensitive”, “software upgrade”, “problem” and “needs action”
string
required
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”)
string
mainnet, testnet or devnet
string[]
Array of clients this feed corresponds to depending on the chain. Currently 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
Size of a single page i.e how many records to send back in the response
integer
Page number
APIError Response Object Schema
APIError Response Object Schema
ApiError