Blockchain Intelligence APIs: GET Node Updates

  curl --request GET \
  --url https://web-backend.scale3production.com/node_updates \
  --header 'x-api-key: <api-key>' \
  --header 'x-user-agent: s3l-web-client'

{
  "result": [
    {
      "_id": "64caad9ff235e4337cabb497",
      "name": "mainnet-v1.6.3",
      "chain": "sui",
      "category": "optional",
      "description": "The upgrade includes new linter warnings for custom transfer/share/freeze functions, support for selective suppression of linter warnings, changes in unit tests handling, a new TransactionKindIn filter for querying transaction blocks, and linter warnings for object transfers.",
      "repo_name": "sui",
      "tag": "mainnet-v1.6.3",
      "network": "mainnet",
      "client": "sui",
      "release_date": 1690959709,
      "release_notes_url": "https://github.com/MystenLabs/sui/releases/tag/mainnet-v1.6.3",
      "build_artifacts": [],
      "createdAt": 1691004319,
      "updatedAt": 1691004319,
      "version": "1.6.3",
      "commit_hash": "abc123",
      "priority": "High",
      "prerequisites": ["Previous version installed"],
      "breaking_changes": false,
      "breaking_change_summary": "No breaking changes",
      "upcoming_network_upgrade": "None",
      "required_for_upcoming_upgrade": false
    }
  ],
  "metadata": {
    "page": 1,
    "page_size": 10000,
    "total_pages": 1
  }
}

{
  "error": {
    "message": "Invalid api key unauthorized",
    "status": 401
  }
}

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.
GET /node-updates?chain=eth&network=mainnet&breaking_changes=true&sort=priority,-release_date
Pagination and Selective Fields:: Retrieve the second page of updates, showing 10 records per page, displaying only name, version, and release date.
GET /node-updates?page=2&page_size=10&fields=name,version,release_date

Check out the api-query-params documentation for more information on how to use these query parameters. For any questions or feedback regarding the use of query parameters with our API, feel free to reach out to our support team at support@scale3labs.com. The complete list of query parameters supported by the ‘GET Node Updates’ endpoint is provided below.

string

Node update category

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

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: ( “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”)

string

Version of the node update

string

Priority/Severity level of the node update

boolean

Boolean indicating if the update has breaking changes

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

NodeUpdate[]

Hide Node Update Object Properties

string

required

Name of the node update

string

required

Node update category

string

required

Node update chain

string

required

Node update description

string

required

Name of repository that contains the update code

string

required

Node update tag. The Tag contains the update version

string

required

Node update network (mainnet, testnet, devnet)

string

required

Node update client depending on the chain. For chains with no client the default value is the chain itself

integer

required

Release date of the update (unix epoch timestamp)

string

required

Link to github repository release notes

BuildArtifact[]

required

Hide Build Artifact Object Properties

string

required

Build artifact type (docker, genisis or node)

string

required

Node update binary download url

string

Node update binary compatible os

string

Node update binary md5

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

Hide Metadata Object Properties

integer

required

Size of a single page i.e how many records to send back in the response

integer

required

Page number

integer

required

Total pages with the given page_size

APIError Response Object Schema

ApiError

Hide ApiError Object Properties

string

required

Error message

integer

required

Http status code

ApiError[]

Array of errors which led to the error

  curl --request GET \
  --url https://web-backend.scale3production.com/node_updates \
  --header 'x-api-key: <api-key>' \
  --header 'x-user-agent: s3l-web-client'

{
  "result": [
    {
      "_id": "64caad9ff235e4337cabb497",
      "name": "mainnet-v1.6.3",
      "chain": "sui",
      "category": "optional",
      "description": "The upgrade includes new linter warnings for custom transfer/share/freeze functions, support for selective suppression of linter warnings, changes in unit tests handling, a new TransactionKindIn filter for querying transaction blocks, and linter warnings for object transfers.",
      "repo_name": "sui",
      "tag": "mainnet-v1.6.3",
      "network": "mainnet",
      "client": "sui",
      "release_date": 1690959709,
      "release_notes_url": "https://github.com/MystenLabs/sui/releases/tag/mainnet-v1.6.3",
      "build_artifacts": [],
      "createdAt": 1691004319,
      "updatedAt": 1691004319,
      "version": "1.6.3",
      "commit_hash": "abc123",
      "priority": "High",
      "prerequisites": ["Previous version installed"],
      "breaking_changes": false,
      "breaking_change_summary": "No breaking changes",
      "upcoming_network_upgrade": "None",
      "required_for_upcoming_upgrade": false
    }
  ],
  "metadata": {
    "page": 1,
    "page_size": 10000,
    "total_pages": 1
  }
}

{
  "error": {
    "message": "Invalid api key unauthorized",
    "status": 401
  }
}

Home

Intel

Alerting

Monitoring

Logging

Nodepilot

Blockchain Node Setup

Command Line Interface

Blockchain Intelligence APIs: GET Node Updates

Using Query Parameters with GET Node Updates

Examples of Query Parameters

​Using Query Parameters with GET Node Updates

​Examples of Query Parameters

Using Query Parameters with GET Node Updates

Examples of Query Parameters