Overview
Bitnob Enterprise operates shared, multi-tenant RPC endpoints for every supported chain so you don't have to run your own nodes. Each org gets a per-day request quota. All routes require an API key with the nodes:read or nodes:manage permission as noted.
List Chain Endpoints
Use Case
Returns every chain Bitnob Enterprise serves, with per-network endpoint URLs and your org's daily usage stats. Permission: nodes:read.
List Chain Endpoints Response
Array of every chain Bitnob Enterprise serves RPC for. One entry per chain, each carrying its list of per-network endpoints.
Stable internal identifier for the chain — used by the get-chain-details endpoint and referenced from `WalletResponse.chain_id`.
Lowercase chain alias used everywhere else in the API (`ethereum`, `bitcoin`, `tron`, `solana`, etc.). Pass this in URLs when sending JSON-RPC requests.
Display-friendly chain name suitable for UIs (e.g. `"Ethereum"`, `"Tron"`).
Per-network entries (mainnet + any testnets) — each carries its own URL, status, and quota counters so you can pick the right one for a given environment.
Network slug within the chain (`mainnet`, `sepolia`, `testnet`, `nile`, etc.). Combine with `chain` to build the `chain_network` path used in JSON-RPC requests.
Full RPC URL for this chain/network. Use it as the target when sending JSON-RPC requests, or as a `provider` URL inside SDKs like ethers/web3.
Whether the network is a testnet — useful for gating production traffic away from non-mainnet endpoints.
Whether the endpoint is currently serving traffic. A `false` value indicates the endpoint is temporarily disabled for maintenance — fall back to another network or retry later.
Number of requests your organisation has already sent to this endpoint today (UTC). Resets at 00:00 UTC; use it to monitor how close you are to the quota.
Maximum number of requests your organisation can send to this endpoint per UTC day. Exceeding it returns rate-limit errors — contact support to raise the quota.
Get Chain Details
Use Case
Returns metadata for a single chain (by chain UUID). Permission: nodes:read.
Get Chain Details Response
Returns the single Chain object whose chain_id matches the path parameter — same field shape as one element of the List Chain Endpoints Response array (chain_id, chain, chain_label, and the endpoints[] list with quota counters). Returns 404 if the chain is not registered for your organisation.
Send a JSON-RPC Request
Use Case
Sends a JSON-RPC request to the Bitnob Enterprise-operated node for the given chain/network. The path segment chain_network follows the alias-network convention shown in rpc_endpoint (e.g., eth-mainnet, btc-mainnet, sol-mainnet-beta, tron-mainnet, polygon-mainnet). Permission: nodes:manage.
Request Body
Standard JSON-RPC envelope.
Send JSON-RPC Response
JSON-RPC protocol version — always `"2.0"`. Echoed verbatim so client libraries can validate the envelope.
Echo of the request `id`. Match it against your outgoing request to correlate responses when multiplexing calls.
Method-specific payload from the node — its shape depends on the method (hex string for `eth_blockNumber`, transaction object for `eth_getTransactionByHash`, etc.). Present only on success.
JSON-RPC error envelope `{ code, message, data? }` returned when the call fails. Mutually exclusive with `result` — check this branch before unwrapping `result`.
Each call counts toward your daily quota; once exhausted the endpoint returns 429.