Files
ritmex-bot/docs/grvt/schemas/api_transfer_history_request.md

1.6 KiB

!!! info "ApiTransferHistoryRequest" The request to get the historical transfers of an account
The history is returned in reverse chronological order

Pagination works as follows:

  • We perform a reverse chronological lookup, starting from end_time. If end_time is not set, we start from the most recent data.
  • The lookup is limited to limit records. If more data is requested, the response will contain a next cursor for you to query the next page.
  • If a cursor is provided, it will be used to fetch results from that point onwards.
  • Pagination will continue until the start_time is reached. If start_time is not set, pagination will continue as far back as our data retention policy allows.

|Name<br>`Lite`|Type|Required<br>`Default`| Description |
|-|-|-|-|
|currency<br>`c` |[string]|True|The token currency to query for, if nil or empty, return all transfers. Otherwise, only entries matching the filter will be returned|
|start_time<br>`st` |string|False<br>`0`|The start time to query for in unix nanoseconds|
|end_time<br>`et` |string|False<br>`now()`|The end time to query for in unix nanoseconds|
|limit<br>`l` |integer|False<br>`500`|The limit to query for. Defaults to 500; Max 1000|
|cursor<br>`c1` |string|False<br>`''`|The cursor to indicate when to start the next query from|
|tx_id<br>`ti` |string|False<br>`0`|The transaction ID to query for|
|main_account_id<br>`ma` |string|False<br>``|Main account ID being queried. By default, applies the requestor's main account ID.|