Monero RPC API

XMR · monero dialect

JSON-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.

Only these methods are available; wallet, peer, node-control and UTXO-set scan methods are not. Every call counts as one unit.

• get_alternate_chains
• get_block
• get_block_count
• get_block_header_by_hash
• get_block_header_by_height
• get_block_headers_range
• get_coinbase_tx_sum
• get_fee_estimate
• get_info
• get_last_block_header
• get_miner_data
• get_output_distribution
• get_output_histogram
• get_txpool_backlog
• get_version
• hard_fork_info
• on_get_block_hash

At a limit the gateway answers HTTP 429 with Retry-After. Pricing · Status · OpenAPI description · Monero on Olenza Explorer

Other chains: Bitcoin Ethereum Litecoin Dogecoin Bitcoin Cash eCash Zcash Decred