Sign in

v1

latestOpenAPI 3.0.32026-07-24707482.9 KB
RPC

Fusion L2 JSON-RPC

Proxies a JSON-RPC 2.0 request to the Fusion L2 OP-Geth node. This route is for the Fusion L2 only. Only Fusion L2 methods are supported — JSON-RPC for any other connected chain must go to the Fusion Proxy's multi-DLT endpoint /dlts/{dlt}/networks/{networkId}/rpc/{apiKey} (see the fusion-proxy spec).

Authentication is accepted via the Overledger-issued API key as the {apiKey} path segment, the X-API-Key header, or an Authorization: Bearer <jwt> Keycloak token. The X-API-Key header takes precedence over the others when present.

post/rpc/{apiKey}

Path parameters

apiKeystring required

An Overledger-issued API key (fk_<keyId>.<secret>) used to authenticate the request.

Request body

jsonrpc'2.0' required
methodstring required

Example request

{
  "method": "eth_blockNumber",
  "params": []
}

Response

JSON-RPC response (success or RPC-level error)

OR