Using blockchain nodes

This page describes how to get ready to query a Blockchain Node Engine node using an API key for authentication.

Before you can use the blockchain node, you need to:

Create an API key

You must use an API key for authentication to query your node.

To generate a key in the Google Cloud console:

  1. In the Google Cloud console, go to the APIs & Services, Credentials page.

    Go to Credentials

  2. Click Create credentials.

  3. Click API key.

  4. In the API key created dialog, click Copy to copy the key, and then paste it into a temporary file. You will need the API key in Query a blockchain node.

See Authenticate using API keys for more information on API keys.

Get the blockchain node endpoint URLs

You can get the blockchain node URLs using the console or by sending an API request:

Using the console

To view details about a node in the UI:

  1. In the Google Cloud console, go to the Blockchain Node Engine page.

    Go to Blockchain Node Engine

  2. The Nodes list page is displayed by default.

  3. Click a node name. The Node details page is displayed.
    Blockchain node URLs are displayed in the Endpoints area.

Using an API

To list details related to a blockchain node with ListBlockchainNodes, send the following request:

curl \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  -H "Content-Type: application/json" \\


Private Service Enabled Nodes

NOTE: This section only applies to Private Service Connect nodes. All other nodes can proceed to the next section

Private Service Connect enabled nodes will return a serviceAttachment as shown in the following Ethereum example:

  "name": "projects/cloud-web3/locations/us-central1/blockchainNodes/my-node",
  "createTime": "2023-12-08T15:06:43.538015Z",
  "updateTime": "2023-12-08T15:23:53.016239Z",
  "blockchainType": "ETHEREUM",
  "connectionInfo": {
    "serviceAttachment": "projects/associated-project/regions/us-central1/serviceAttachments/associated-service-attachment"
  "ethereumDetails": {
    "network": "MAINNET",
    "nodeType": "ARCHIVE",
    "executionClient": "ERIGON",
    "consensusClient": "LIGHTHOUSE",
    "apiEnableAdmin": false,
    "apiEnableDebug": false
  "state": "RUNNING",
  "pscOnly": true

To use the node, complete the Private Service Connect configuration. Then construct your endpoint using the Private Service Connect static IP address and designated port for your chosen interaction, in place of the standard DNS endpoint.

For port number references:

Nodes with a Public Endpoint

The blockchain URLs returned are in the endpointInfo and additionalEndpoints sections as shown in the following Ethereum example:

  "name": "projects/my-project-id/locations/us-central1/blockchainNodes/my-node",
  "createTime": "2023-05-05T04:24:12.432769Z",
  "updateTime": "2023-05-05T05:03:02.561240Z",
  "labels": {
    "my-label-key": "my-label-value"
  "blockchainType": "ETHEREUM",
  "connectionInfo": {
    "ipInfo": {
      "rpcIpv4Address": ""
    "endpointInfo": {
      "jsonRpcApiEndpoint": "",
      "websocketsApiEndpoint": ""
  "ethereumDetails": {
    "network": "MAINNET",
    "nodeType": "FULL",
    "executionClient": "GETH",
    "consensusClient": "LIGHTHOUSE",
    "apiEnableAdmin": false,
    "apiEnableDebug": false,
    "additionalEndpoints": {
      "beaconApiEndpoint": "",
      "beaconPrometheusMetricsApiEndpoint": ""
  "state": "RUNNING"

See also: View blockchain node details, Using an API

Query a blockchain node

Now that you know your API key and blockchain node endpoint URLs, for usage instructions see the appropriate topic for each blockchain: