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.

Path Params
string
required

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

Body Params
string
enum
required
Allowed:
string
required
required
params
array
params
Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json