Hedera
Query the Hedera Hashgraph network — accounts, tokens, topics, and transactions — without an SDK
hedera) exposes read operations against the free, public Hedera Mirror Node REST API as workflow steps. No signing credential or third-party SDK is required for any operation on this page — everything here is a read.
Quick Start
- Add a Hedera node to your workflow
- Set
resourcetoaccountandoperationtogetBalance - Enter an
accountId(e.g.0.0.98) - Leave
networkunset to use the default (testnet), or set it explicitly - Run the workflow — the node returns the account's HBAR balance and held tokens
resource, operation, network — plus a small set of
operation-specific fields. Learn the pattern once on Input & Output
and every operation below follows it.
Pages in This Guide
Configuration
appsettings.json, default network, and dependency registration.
Networks
Mainnet, testnet, previewnet, and adding a custom network.
Account Operations
getBalance and getInfo — HBAR balances and account metadata.
Token Operations
HTS token metadata and an account's token holdings.
Topic Operations
HCS topic messages, ordering, and pagination.
Transaction Operations
Look up a transaction's status, result, and fee.
Utility Operations
Unit conversion and address validation.
Input & Output
The shared config-key pattern and how errors surface.
Examples
Worked workflow patterns using this node.
Troubleshooting
Common errors and how to fix them.
Roadmap
Signed writes — what's coming and what it needs.
Core Concepts
Mirror Node Reads
Every operation on this node queries Hedera's Mirror Node REST API — a free, public, eventually-consistent index of network state. That means no wallet, no signing key, and no per-request fee for any operation documented here. It also means data can lag live consensus by a few seconds; see Troubleshooting.
Resources
Operations are grouped by resource, matching Hedera's own service boundaries:
- account — HBAR balances and account metadata
- token — Hedera Token Service (HTS) fungible/non-fungible tokens
- topic — Hedera Consensus Service (HCS) message topics
- transaction — individual transaction lookups
- utility — local helpers (unit conversion, address validation) that don't call the network
Networks
Every operation runs against one of three Hedera networks, selected per-call via the network config key. See Networks for URLs and defaults.
Operation Summary
| Resource | Operation | Guide Page |
|---|---|---|
account | getBalance, getInfo | Account Operations |
token | getInfo, getBalances | Token Operations |
topic | getMessages | Topic Operations |
transaction | get | Transaction Operations |
utility | convertUnits, validateAddress | Utility Operations |