Monero RPC API
XMR · monero dialectJSON-RPC to our own Monero full node, with one Olenza API key. Monero daemon JSON-RPC (monerod /json_rpc): the gateway passes your call to the node and its answer back unchanged; it does not translate between dialects.
monerod JSON-RPC. Only /json_rpc methods are available; monerod's separate binary endpoints (/get_outs, /getblocks.bin) are not, so a light wallet cannot sync through this route.
Endpoint
POST https://node.olenza.io/v1/rpc/xmr
Send the key in the X-API-Key header (or Authorization: Bearer). A batch is a JSON array of calls.
Example
curl https://node.olenza.io/v1/rpc/xmr \
-H "X-API-Key: $OLENZA_KEY" \
--data '{"jsonrpc":"2.0","id":"0","method":"get_block_count"}'
The answer is the node's own JSON-RPC response. Errors from the gateway carry a stable error.data.reason — see the docs.
Available methods
16 methodsOnly these methods are available; wallet, peer and node-control methods are not. Every call counts as one unit.
get_alternate_chainsget_blockget_block_countget_block_header_by_hashget_block_header_by_heightget_block_headers_rangeget_coinbase_tx_sumget_fee_estimateget_infoget_last_block_headerget_miner_dataget_output_distributionget_output_histogramget_versionhard_fork_infoon_get_block_hash
Limits
free| Requests / s | Burst | Units / day | Units / month | Batch |
|---|---|---|---|---|
| 5 | 10 | 10,000 | 300,000 | 5 |
Olenza is free. At a limit the gateway answers HTTP 429 with Retry-After. Limits · Status · OpenAPI description · Monero on Olenza Explorer