You
Software and troubleshooting

Getting started with the pool API

Last updated: 5 November 2026

Read live pool and per-miner stats from the public JSON API: the two endpoints, how to query your own address, and how often to poll.

What can I do with the pool API?

The pool has a public, read-only JSON API that serves everything the dashboard shows. It needs no key and no account.

You can use it to build your own monitoring, a home dashboard, a bot, or a spreadsheet that tracks your mining. It gives you two kinds of data:

  • Pool-wide stats: hashrate, network difficulty, blocks and payments.
  • Per-miner stats for any address.
A curl request to the pool stats address, with the pool host and the endpoint marked in colour. Below it is the JSON answer. Its pool section holds hashrate, miners and workers, and its network section holds difficulty and height.
The address names the pool and the figures you want. The answer is plain JSON, grouped into the pool and the network.

How do I get the pool-wide stats?

The pool stats endpoint returns the same figures you see in the header and on the dashboard:

  • Pool and network hashrate.
  • Connected miners.
  • Difficulty.
  • The last blocks.
  • Recent payments.

Fetch it like any JSON URL:

Pool stats 
curl https://qubitcoin.herominers.com/api/stats

How do I get stats for my own address?

To read one address, pass it to the miner stats endpoint. Replace YOUR_QTC_ADDRESS with your wallet address.

The response holds that address's hashrate, workers, balances and recent payments. It is the raw data behind your dashboard page:

Miner stats 
curl https://qubitcoin.herominers.com/api/stats_address?address=YOUR_QTC_ADDRESS

How often should I poll the API?

Once every minute or two is plenty. The API is there to be used, but poll it politely.

An API answer card refreshed on a clock. Above, a dense burst of requests is crossed out in red because every answer is the same. Below, one request per clock tick, spaced out, gets a green tick.
The figures refresh every so often, so one request every minute or two is enough.

The numbers behind it only update every so often. Polling far more often wastes bandwidth on both sides and gives you no fresher data.

Cache what you fetch. Build around the same update cadence the dashboard uses.

Ready to put this into practice?
The How to Mine guide picks your closest server and builds your exact miner command.
Start Mining Qubitcoin