Exonum Node HTTP API

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