/eth/v1/events

Subscribe to beacon node events

curl -X GET \
    "https://mainnet.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/eth/v1/events?topics=head" \
    -H "accept: text/event-stream"

curl -X GET \
    "https://sepolia.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>/eth/v1/events?topics=head" \
    -H "accept: text/event-stream"

Previous/eth/v1/beacon/states/{state_id}/validators/{validator_id}Next/eth/v1/validator/aggregate_attestation

Last updated 2 months ago

Was this helpful?

Subscribe to beacon node events

Provides endpoint to subscribe to beacon node Server-Sent-Events stream. Consumers should use eventsource implementation to listen on those events.

Servers may send SSE comments beginning with : for any purpose, including to keep the event stream connection alive in the presence of proxy servers.

get

/eth/v1/events

Query parameters

topicsstring · enum[]required

Event types to subscribe to

Responses

text/event-stream

application/json

cURL

JavaScript

Python

HTTP

curl -L \
  --url 'https://mainnet.ethereum.validationcloud.io/v1/<YOUR_API_KEY_HERE>//eth/v1/events?topics=head'

200

400

500

head

block

attestation

voluntary_exit

finalized_checkpoint

chain_reorg

contribution_and_proof

event: head
data: {"slot":"10", "block":"0x9a2fefd2fdb57f74993c7780ea5b9030d2897b615b89f808011ca5aebed54eaf", "state":"0x600e852a08c1200654ddf11025f1ceacb3c2e74bdd5c630cde0838b2591b69f9", "epoch_transition":false, "previous_duty_dependent_root":"0x5e0043f107cb57913498fbf2f99ff55e730bf1e151f02f221e977c91a90a0e91", "current_duty_dependent_root":"0x5e0043f107cb57913498fbf2f99ff55e730bf1e151f02f221e977c91a90a0e91", "execution_optimistic": false}

Opened SSE stream.