REST API
Hgraph serves the Hedera mirror node REST API from its own bare-metal infrastructure. The request and response shapes are the upstream mirror node's, so anything written against a public mirror node works unchanged — you swap the host and add an API key.
curl -s -H "X-API-KEY: <YOUR_API_KEY>" \
https://hedera.hgraph.com/api/v1/accounts/0.0.800
| Network | Base URL |
|---|---|
| Mainnet | https://hedera.hgraph.com/api/v1 |
| Testnet | https://hedera-testnet.hgraph.com/api/v1 |
Authentication is the same as every other Hgraph API — see Endpoints & Authorization. Rate limits are per API key and shared across GraphQL, REST, and JSON-RPC; see Rate Limits & Quotas.
Resources
| Resource | What it returns |
|---|---|
/accounts | Accounts, balances, allowances, airdrops, and per-account rewards |
/balances | Account balance snapshots at a consensus timestamp |
/blocks | Record file blocks |
/contracts | Contracts, contract results, logs, state, and contracts/call |
/network | Exchange rate, fees, stake, supply, and node information |
/schedules | Scheduled transactions |
/tokens | Token definitions, balances, and NFTs with their serials |
/topics/{id} | Consensus topics and their messages |
/transactions | Transactions by ID, timestamp, or account |
For the full parameter, filter, and response reference, see the upstream specification — Hgraph tracks it directly rather than restating it here, so it cannot drift:
Hedera Mirror Node REST API reference →
Hgraph currently serves mirror node REST v0.156.0. Endpoints added in later upstream releases become available when Hgraph upgrades.
REST or GraphQL?
Both read the same indexed data. Which fits depends on the shape of the request, not the volume.
REST returns a fixed response per endpoint. It is the faster path when you want a well-known record — an account, a transaction, a token — and the standard response already contains the fields you need. It is also what most existing Hedera tooling expects.
GraphQL lets you name exactly the fields you want and traverse related records in one round trip, which is the difference between one request and several when you need, say, a token plus its holders plus their recent transfers. It also supports subscriptions for live updates, and reaches tables the REST API does not expose at all — the ERC indexer, DEX, lending, and oracle schemas. See the schema reference for the full surface.
A common split: REST for the record lookups your app already knows how to consume, GraphQL for anything aggregate, relational, or live.
Data formats
REST returns entity IDs in 0.0.x form and timestamps as seconds.nanoseconds strings. This differs from the GraphQL API, which returns bare integers for both — see Data Formats if you consume both.