getEventsBlocks

/events/blocks allows the caller to query a sequence
of BlockEvents indicating which blocks were added and
removed from storage to reach the current state.
Following BlockEvents allows lightweight clients to update
their state without needing to implement their own syncing
logic (like finding the common parent in a reorg).

/events/blocks is considered an "indexer" endpoint
and Rosetta implementations are not required to complete it
to adhere to the Rosetta spec. However, any Rosetta "indexer"
MUST support this endpoint.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

EventsBlocksRequest is utilized to fetch a sequence of BlockEvents
indicating which blocks were added and removed from storage to
reach the current state.

network_identifier
object
required

The network_identifier specifies which network a particular object is associated with.

int64
≥ 0

offset is the offset into the event stream to sync events from. If this
field is not populated, we return the limit events backwards from tip.
If this is set to 0, we start from the beginning.

int64
≥ 0

limit is the maximum number of events to fetch in one call. The implementation
may return <= limit events.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json