One witness by account: votes, rank, missed, parameters
API · /hivewitness-api
Hive Witnesses & Consensus API
The Hive blockchain's delegated-proof-of-stake consensus — the witness election — live from the public Hive RPC nodes, no key, nothing cached. Hive is secured by 20 elected witnesses plus a rotating backup, voted in by HIVE holders with their staked (vested) weight; witnesses produce the blocks, publish the HBD price feed and set the chain parameters. The Hive content reader covers accounts, posts and communities, but not the witness consensus; this opens it. Rank the witnesses by vote weight, each with its vote total converted to HIVE Power, missed block count, running node version, published HBD price feed and the chain parameters it sets. Look up a single witness by account for its votes, rank and production. And read a live network overview — the head block, the current witness producing it, witness participation over the last 128 slots, the total vesting (staking) fund and the HIVE-per-MVESTS rate. The consensus-and-governance layer for Hive wallets, witness dashboards, voters and analytics. Live from api.hive.blog and peer nodes.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 307 ms
- Server probes · 24h
- Subscribers
- 4,606
- active
- Total calls
- 24
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 7,250 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 7.25k calls/month
- 3 req/sec
- All endpoints
- No credit card
Starter
€9.70 /month
- 143,000 calls / month
- 9 requests / second
- Hard cap (429 above quota, no overage)
- 143k calls/month
- 9 req/sec
- Email support
Pro
€33.00 /month
- 795,000 calls / month
- 22 requests / second
- Hard cap (429 above quota, no overage)
- 795k calls/month
- 22 req/sec
- Priority support
Business
€91.50 /month
- 5,200,000 calls / month
- 55 requests / second
- Hard cap (429 above quota, no overage)
- 5.2M calls/month
- 55 req/sec
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Hive Engine API
Live data from the Hive-Engine smart-contract sidechain — a Layer-2 token registry and decentralized exchange built on the Hive blockchain. Look up any Hive-Engine token's on-chain registry record (issuer, precision, max / current / circulating supply, staking status and total staked), read its live DEX market metrics (last price in HIVE, highest bid, lowest ask, 24h volume and the day's price change), pull the richlist of its largest holders with their liquid balance, staked amount and delegations, and stream the most recent fills on its HIVE market (buyer, seller, quantity, price and time). Symbols are Hive-Engine tokens such as LEO, BEE, SWAP.HIVE or SPS; prices and market volume are denominated in HIVE, the base-chain coin. This is the token-sidechain / on-chain-DEX view — per-token supply, holders and an internal order-book market — distinct from the single-venue exchange tickers, the cross-exchange coin-markets and the base-chain on-chain APIs in the catalogue. Live and read straight from a public Hive-Engine RPC node — nothing stored.
api.oanor.com/hiveengine-api
Hive API
Live data for the Hive blockchain social network, served straight from Hive's public JSON-RPC nodes — no key, no account, nothing cached. Hive is a decentralised blogging and social platform where posts and votes live on-chain and earn crypto rewards. The account endpoint resolves a username to its profile: display name, reputation score, follower and following counts, post count, bio, location, website and join date — @gtg ("Gandalf the Grey") has a 76 reputation and over ten thousand followers. The posts endpoint returns a user's blog posts with each post's up-vote count, the HBD payout it earned, the comment count, the tags and a link. The trending endpoint returns the platform's trending (or hot, new or top-paid) posts right now, optionally filtered by tag — the front page of Hive. This is the profile-posts-and-trends layer for any decentralised-social, blogging or web3 app. Live from the Hive blockchain, nothing stored. Distinct from other social and centralised-blog APIs — this is the on-chain Hive network. 4 endpoints.
api.oanor.com/hive-api
Tron Super Representatives & Voting API
Tron's delegated-proof-of-stake governance — the Super Representative (SR) election — live from the public TronScan API, no key, nothing cached. Tron is run by 27 elected Super Representatives who produce the blocks, chosen by TRX holders who freeze TRX into votes; below them sit roughly 100 SR partners and candidates waiting to rotate in. The base Tron reader covers accounts and transactions, but not the SR election; this opens it. Rank the SRs and candidates by votes, each with its block production, missed blocks, produce rate and latest block. Look up a single SR by address for its votes, rank and production. And read a live election overview — the active 27, the candidate pool, the total frozen-TRX votes cast across all witnesses and the all-time blocks produced. The validator-and-voting layer for Tron wallets, staking dashboards, voters and analytics. Live from apilist.tronscanapi.com.
api.oanor.com/tronsr-api
EOS API
Live on-chain data from the EOS network (EOS), a delegated-proof-of-stake blockchain with a distinctive resource model where accounts stake EOS for CPU and network bandwidth and buy RAM for state: an account's liquid EOS balance, EOS staked for CPU and network, RAM quota and usage and live resource limits; the block producers ranked by DPoS vote weight; the live chain head, last irreversible block and current producer; and any account's balance of any EOS token.
api.oanor.com/eos-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Hive Witnesses & Consensus API?
What's the rate limit for Hive Witnesses & Consensus API?
How much does Hive Witnesses & Consensus API cost?
Can I cancel my subscription anytime?
Is Hive Witnesses & Consensus API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/hivewitness-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/hivewitness-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/hivewitness-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/hivewitness-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.