api-access

Repository

panda-pulse

Docs about EF devops team operated mainnet (or testnet) nodes API access

API Access for Mainnet Nodes

Authentication to access the node's API is required. If you don't yet have an API key and you would like to make a query the mainnet nodes contact Barnabas directly or the ethpandaops team. Authentication tokens have to be passed as a header. The current available URLs are as follows:

Execution Layer Clients

https://rpc.mainnet.ethpandaops.io

• Direct the API call to any EL clients in either of the two regions (Europe or North America)

Consensus Layer Clients

https://beacon.mainnet.ethpandaops.io

• Direct the API call to any CL clients via dugtrio in either of the two regions (Europe or North America)

Region specific API call

We currently operate in 2 regions, Europe (Berlin) and North America (Boulder).

If you would like to target speicifc regions, you can do this by using the na1 or eu1 prefix.

Example:

• https://rpc.mainnet.eu1.ethpandaops.io
• https://beacon.mainnet.na1.ethpandaops.io

NOTE If you do not specify the region, it will be targetting the eu1 servers.

Currently available endpoints for consumption:

Mainnet

Consensus layer calls

• https://teku.mainnet.eu1.ethpandaops.io or https://teku.mainnet.na1.ethpandaops.io
• https://prysm.mainnet.eu1.ethpandaops.io or https://prysm.mainnet.na1.ethpandaops.io
• https://nimbus.mainnet.eu1.ethpandaops.io or https://nimbus.mainnet.na1.ethpandaops.io
• https://lighthouse.mainnet.eu1.ethpandaops.io or https://lighthouse.mainnet.na1.ethpandaops.io
• https://lodestar.mainnet.eu1.ethpandaops.io or https://lodestar.mainnet.na1.ethpandaops.io
• https://grandine.mainnet.eu1.ethpandaops.io or https://grandine.mainnet.na1.ethpandaops.io

Execution layer calls

• https://geth.mainnet.eu1.ethpandaops.io or https://geth.mainnet.na1.ethpandaops.io
• https://besu.mainnet.eu1.ethpandaops.io or https://besu.mainnet.na1.ethpandaops.io
• https://nethermind.mainnet.eu1.ethpandaops.io or https://nethermind.mainnet.na1.ethpandaops.io
• https://erigon.mainnet.eu1.ethpandaops.io or https://erigon.mainnet.na1.ethpandaops.io
• https://reth.mainnet.eu1.ethpandaops.io or https://reth.mainnet.na1.ethpandaops.io
• https://archive.mainnet.ethpandaops.io (Erigon or Reth archive nodes)

Hoodi/Sepolia

Consensus layer calls

• https://beacon.hoodi.ethpandaops.io (load balanced between eu1 and na1) or https://beacon.hoodi.na1.ethpandaops.io or https://beacon.hoodi.eu1.ethpandaops.io

Execution layer calls

• https://rpc.hoodi.ethpandaops.io (load balanced between eu1 and na1) or https://rpc.hoodi.na1.ethpandaops.io or https://rpc.hoodi.eu1.ethpandaops.io

Examples

• Directs the API call to any geth-CL node (note CL will be round robin selected) - execution layer API endpoint, aimed at geth endpoint: https://geth.mainnet.ethpandaops.io
• Directs an API call to lighthouse-EL node (note EL will be round robin selected) - beacon API specific call aimed at lighthouse endpoint: https://lighthouse.mainnet.ethpandaops.io
• Directs an API call to geth-lighthouse node - execution layer API endpoint, aimed at geth endpoint: https://geth-lighthouse.mainnet.ethpandaops.io
• Directs an API call to lighthouse-geth node - beacon API specific call aimed at lighthouse endpoint: https://lighthouse-geth.mainnet.ethpandaops.io

curl \
  --data '{"method":"web3_clientVersion","params":[],"id":1,"jsonrpc":"2.0"}' \
  -H "CF-Access-Client-Id: $client_id" \
  -H "CF-Access-Client-Secret: $client_secret" \
  -H "Content-Type: application/json" \
  -X POST https://geth-lighthouse.$network.ethpandaops.io

CL Call

curl \
  -H "CF-Access-Client-Id: $client_id" \
  -H "CF-Access-Client-Secret: $client_secret" \
  https://lighthouse.mainnet.ethpandaops.io/eth/v1/node/version