Links

/eth/v1/beacon/light_client/updates

Get 'LightClientUpdate' instances in a requested sync committee period range.
In the range of sync committee periods [start_period, start_period + count], requesting LightClientUpdate instances prior to the current head sync committee period chosen by fork choice. Either JSON or SSZ-serialized bytes may be returned, depending on the Accept header.
Results as specified in create_light_client_update MUST be provided by servers. They are required to reply with the requested range's earliest known result, at the very least, and to transmit the results in sequential order (by period). There cannot be more results in the response than min(MAX_REQUEST_LIGHT_CLIENT_UPDATES, count).

Example Request and Result for /v1/beacon/light_client/updates

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/beacon/light_client/updates endpoint. Additionally, we present the resulting response containing information about the update instances in a requested sync committee range.

Parameters

Field
Type
Description
start_period*
string
Start point of the range
count*
string
The maximum number of the items returned
The example in this section uses a non-existing project id.
Make sure you replace it with your Ethereum Holesky Beacon endpoint when issuing the API calls.
Don't have a project id? Here's a straightforward guide on how to obtain one!
get
https://eth-holesky-beacon.blastapi.io/<project-id>/
eth/v1/beacon/light_client/bootstrap/<block_root>
Get 'LightClientBootstrap' structure for a requested block root.
Parameters
Query
start_period*
string
1
count*
string
1
Responses
200: OK
Expand for a detailed response example

Curl Request example

curl -X 'GET' \
'https://eth-holesky-beacon.blastapi.io/<project_id>/eth/v1/beacon/light_client/updates?start_period=1&count=1' \
-H 'accept: application/json'