REST API (Hedera Mirror Node)
The Arkhia REST API provides a low-latency reverse proxy that relays REST requests to resilient, auto-scalable Hedera Mirror Node REST API services.
It offers enhanced performance with reduced throttling, higher availability, and comprehensive dashboard features compared to public mirror nodes.
Authentication
All requests require an API key in the header:
'x-api-key': YOUR_API_KEY
Core Endpoints
Accounts
Get Account Information: GET /accounts/{id}
- Parameters:
id
(string) - Account ID in format 0.0.123456 - Returns: Account balance, keys, expiry timestamp, and auto-renew period
List Accounts: GET /accounts
- Query Parameters:
limit
(1-100, default: 25)order
(asc/desc, default: asc)account.id
(string) - Filter by account IDaccount.balance
(string) - Filter by balance with operators (gt:, gte:, lt:, lte:)
Transactions
Get Transaction: GET /transactions/{transactionId}
List Transactions: GET /transactions
- Query Parameters:
account.id
(string) - Filter by account IDtimestamp
(string) - Filter by timestamp rangetransactiontype
(string) - Filter by transaction typeresult
(string) - Filter by result (SUCCESS, FAIL, etc.)limit
(1-100, default: 25)order
(asc/desc)
Tokens
Get Token Information: GET /tokens/{tokenId}
List Tokens: GET /tokens
Topics (HCS)
Get Topic Information: GET /topics/{topicId}
Get Topic Messages: GET /topics/{topicId}/messages
Documentation & Resources
- REST API Swagger Documentation (Mainnet): Complete API specification
- REST API Swagger Documentation (Testnet): Testing environment specification
Ready to integrate? Check out our REST API Getting Started Guide for step-by-step implementation examples and code samples.
Supported Operations
Account Operations: Information retrieval, balance queries, transaction history, token associations, allowances
Transaction Services: Submission, tracking, history, receipts, batch operations
Token Operations: Creation, management, transfers, NFT operations, supply management