uptime - Bitcoin Cash

Example code for the uptime JSON-RPC method. Complete guide on how to use the uptime JSON-RPC method in the GetBlock Web3 documentation.

This method returns the total number of seconds the node has been running since it was last started.

Parameters

This method does not accept any parameters.

Request

cURL

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "uptime",
    "params": [],
    "id": "getblock.io"
}'

bitcoinjs-lib

example.js

const axios = require('axios');
const { data } = await axios.post('https://go.getblock.io/<ACCESS-TOKEN>/', {
  jsonrpc: '2.0', method: 'uptime', params: [], id: 'getblock.io'
});
console.log(data.result);

Request

example.py

import requests

response = requests.post(
    'https://go.getblock.io/<ACCESS-TOKEN>/',
    headers={'Content-Type': 'application/json'},
    json={
        'jsonrpc': '2.0',
        'method': 'uptime',
        'params': [],
        'id': 'getblock.io'
    }
)

print(response.json()['result'])

Rust

example.rs

use reqwest::Client;
use serde_json::{json, Value};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = Client::new();

    let response = client
        .post("https://go.getblock.io/<ACCESS-TOKEN>/")
        .header("Content-Type", "application/json")
        .json(&json!({
            "jsonrpc": "2.0",
            "method": "uptime",
            "params": [],
            "id": "getblock.io"
        }))
        .send()
        .await?
        .json::<Value>()
        .await?;

    println!("Result: {}", response["result"]);
    Ok(())
}

Response

{
    "error": null,
    "id": "getblock.io",
    "result": 1834726
}

Response Parameters

Parameter	Type	Description
error	null|object	Error object when the call fails, otherwise null
id	string	Request identifier matching the request
result	numeric	Node uptime in seconds since last start

Use Cases

• Stability Monitoring: Detect unexpected node restarts by watching uptime resets

• SLA Reporting: Track continuous run time for availability reporting

• Health Checks: Confirm a node has been up long enough to be trusted

• Ops Dashboards: Display node uptime alongside sync status

Error Handling

Error Code	Message	Description
-32700	Parse error	Request body is not valid JSON
-32600	Invalid request	The JSON sent is not a valid request object
-32603	Internal error	Node failed to read the requested chain state