get_blobs
Last updated
Last updated
Returns an empty list if no blobs were uploaded during the slot.
Returns null
if the slot has not been completed yet.
Returns an error if there was a database or RPC failure.
Typically, each user is represented by a blober, and each blober’s associated data are its blobs. However, a blober may map to a user account, a node account, or another logical entity—the semantics may vary and is determined by each network’s operators.
POST /get_blobs HTTP/1.1
Host: devnet.indexer.data-anchor.termina.technology
Content-Type: application/json
Accept: */*
Content-Length: 131
{
"id": "42",
"jsonrpc": "2.0",
"method": "get_blobs",
"params": {
"blober": "4Nd1m1c9f9LxFHVfv1m1ChMpV4hV6j3uYVFzh5eRvYV7",
"slot": 12345678
}
}
{
"jsonrpc": "2.0",
"id": "42",
"result": [
[
72,
101,
108,
108,
111
],
[
16,
32,
48,
64,
80
]
]
}