Skip to main content
POST
private/get_subaccount_value_history

Body

application/json

wallet, when set, takes precedence over subaccount_id. The window is unix milliseconds; period is seconds and must be one the sampler's tables cover.

end_timestamp
integer<uint64> | null
Required range: x >= 0
page
integer<uint32> | null
Required range: x >= 0
page_size
integer<uint32> | null
Required range: x >= 0
period
integer<uint64> | null
Required range: x >= 0
start_timestamp
integer<uint64> | null
Required range: x >= 0
subaccount_id
integer<uint64> | null
Required range: x >= 0
wallet
string | null

Response

Success

By-wallet lookups return every owned subaccount's samples, concatenated and tagged with subaccount_id — not a summed wallet total. Coverage is ragged by design: a subaccount contributes no entry for buckets in which it held nothing, rather than reporting a zero it never had. Callers plotting a wallet total must group by subaccount_id and carry each series forward.

pagination
object
required

Response envelope for paginated RPCs.

subaccount_value_history
object[]
required