Api deposit history request
The request to get the historical deposits of an account
The history is returned in reverse chronological order
Both finalized and pending deposits are returned, and pending deposits are indicated by an empty confirmedTime field.
Pagination works as follows:
- We perform a reverse chronological lookup, starting from
end_time. Ifend_timeis not set, we start from the most recent data. - The lookup is limited to
limitrecords. If more data is requested, the response will contain anextcursor for you to query the next page. - If a
cursoris provided, it will be used to fetch results from that point onwards. - Pagination will continue until the
start_timeis reached. Ifstart_timeis not set, pagination will continue as far back as our data retention policy allows.
NameLite |
Type | RequiredDefault |
Description |
|---|---|---|---|
currencyc |
[string] | True | The token currency to query for, if nil or empty, return all deposits. Otherwise, only entries matching the filter will be returned |
start_timest |
string | False0 |
The start time to query for in unix nanoseconds |
end_timeet |
string | Falsenow() |
The end time to query for in unix nanoseconds |
limitl |
integer | False500 |
The limit to query for. Defaults to 500; Max 1000 |
cursorc1 |
string | False'' |
The cursor to indicate when to start the next query from |
main_account_idma |
string | False `` |
Main account ID being queried. By default, applies the requestor's main account ID. |