BitFury

Exonum Node HTTP API

The HTTP surface an Exonum node serves. The explorer service exposes REST endpoints under /api/explorer (blocks, block, transactions, call_status) plus a WebSocket interface for submitting signed transactions and subscribing to block- and transaction-commit events; the system API plugin exposes node info, stats, peers, consensus status and shutdown under /api/system on the private HTTP server; built-in services (supervisor, time oracle) expose their own endpoints under /api/services/{service_name}. Exonum is self-hosted software, so there is no vendor-operated base URL - each operator runs their own node and chooses its public and private ports.

GitHub

Documentation

📖
Documentation
https://exonum.com/doc/version/latest/
📖
APIReference
https://docs.rs/exonum-explorer-service/latest/exonum_explorer_service/api/index.html

Other Resources

🔗
SourceCode
https://github.com/exonum/exonum
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/bitfury-group/refs/heads/main/asyncapi/bitfury-group-exonum-events.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/bitfury-group/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/exonum-node-http-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: bitfury-group:exonum-node-http-api
name: Exonum Node HTTP API
description: The HTTP surface an Exonum node serves. The explorer service exposes REST endpoints under
  /api/explorer (blocks, block, transactions, call_status) plus a WebSocket interface for submitting signed
  transactions and subscribing to block- and transaction-commit events; the system API plugin exposes
  node info, stats, peers, consensus status and shutdown under /api/system on the private HTTP server;
  built-in services (supervisor, time oracle) expose their own endpoints under /api/services/{service_name}.
  Exonum is self-hosted software, so there is no vendor-operated base URL - each operator runs their own
  node and chooses its public and private ports.
humanURL: https://exonum.com/doc/version/latest/
tags:
- Blockchain
- Permissioned Blockchain
- Explorer
- WebSockets
x-deployment: self-hosted
x-deployment-note: No vendor-hosted base URL exists, and none is asserted here; the documentation demonstrates
  the API against a locally run node (public HTTP server 8080, private 8081 in the tutorials).
properties:
- type: Documentation
  url: https://exonum.com/doc/version/latest/
- type: APIReference
  url: https://docs.rs/exonum-explorer-service/latest/exonum_explorer_service/api/index.html
- type: SourceCode
  url: https://github.com/exonum/exonum
- type: Webhooks
  name: Exonum explorer WebSocket event subscriptions (pub/sub; no HTTP webhooks)
  url: asyncapi/bitfury-group-exonum-events.yml