Skip to main content
European CommissionEBSI European Blockchain
Select the Environment you want to work withEnvironment:

Besu JSON-RPC API

Last updated on
POST 

/ledger/v3/blockchains/besu

Hyperledger Besu Ethereum Enterprise Client JSON-RPC API. For some protected methods, the endpoint requires authentication via the Authorisation API. It accepts OAuth2 tokens (for Trusted Apps) or SIOP tokens (for DIDs). The protected methods are:

  • eth_sendRawTransaction
  • eth_estimateGas

Request

Body

required

The body follows the JSON-RPC 2.0 specification. It requires the following fields:

  • jsonrpc: Must be exactly "2.0"
  • method: Hyperledger Besu JSON-RPC native method that is invoked. The list of available methods can be found in the Ledger API technical specifications List of JSON-RPC methods.
  • params: Array of parameters.
  • id: Identifier established by the client.
    jsonrpc stringrequired

    Must be exactly "2.0"

    method stringrequired

    Besu JSON-RPC native method to be invoked

    params object[]required

    Array of parameters

  • Array [
  • oneOf
    boolean
  • ]
  • id integerrequired

    Identifier established by the client

Responses

Response

Schema
    jsonrpc string

    Must be exactly "2.0"

    id integer

    Same identifier established by the client in the call

    result object

    Result of the call

    oneOf
    boolean
    error object

    Error details

    code integer

    Error code

    message string

    Error message

Loading...