Skip to main content
GET
Get user history

Authorizations

Authorization
string
header
required

API token issued by your LootRush account manager. Sent as Authorization: Bearer <token>.

Query Parameters

resource
enum<string>
required

Resource type to query.

Available options:
cards,
account
feature
enum<string>
required

Which data set to return.

Account — the two halves of an account's activity. Every record is in exactly one of them, so they can be read together without double-counting.

  • account — the LEDGER: everything that settled. One node per ledger line, the same lines the CSV/PDF account statement writes for the same period. This is what you reconcile against.
  • account-unsettled — everything that has NOT settled and so appears nowhere in the ledger or the statement: awaiting payment, pending, in analysis, started, rejected. Some of these will settle and move to account; the terminal ones (rejected, canceled) never will. This is where a withdrawal lives between being requested and reaching the ledger.

Account, filtered by kind — subsets of account, same ledger, one operation type each:

  • account-onramp (deposits), account-offramp (withdrawals), account-swap (converts), account-crypto (crypto transfers and sends), account-portifolio (portfolio activity).

Cards:

  • cards-transactions (card transactions), cards-summary (card snapshot, see asOf and status), cards-balance (balance movements per card).
Available options:
account,
account-unsettled,
account-onramp,
account-offramp,
account-swap,
account-crypto,
account-portifolio,
cards-transactions,
cards-summary,
cards-balance
currentPage
integer
default:0

Page number (0-indexed). Pages through the whole result set: there is no depth limit, and no page returns fewer than pageSize items unless it is the last one.

pageSize
integer
default:10

Items per page.

Required range: x <= 200
startDate
string<date-time>

Start of the date window (ISO 8601).

endDate
string<date-time>

End of the date window (ISO 8601).

filterByText
string

Text filter for card transactions (merchant, description).

asOf
string<date-time>

Snapshot date (ISO 8601). Used mainly with cards-summary.

status
enum<string>

Card status filter, for cards-summary only. Omitted, the snapshot returns only the cards still visible to the cardholder — canceled cards are hidden. Use all for every card regardless of status, or a single status to filter by it.

Available options:
all,
active,
inactive,
locked,
canceled

Response

History payload. Shape depends on resource + feature (account history nodes, card transactions, card snapshots, or balance movements). For resource=account the payload is one node per ledger line — the same lines, and the same set of them, that the CSV/PDF account statement writes for the same period, ordered newest first (the reverse of the statement). A cross-chain swap or bridge therefore appears as one node per leg. Two keys per node, and they answer different questions. uniqueHashId is {transactionHash}:{logIndex} — the line's identity on chain: unique per node, stable across calls, and what you reconcile and de-duplicate on. id is the operation the line belongs to, so the two legs of a cross-chain swap share it; it is NOT unique per node, and it is also the value that ties a record here to the same record in account-unsettled before it settled. A line with no on-chain identity gets an opaque unique uniqueHashId instead, or null if it has no key at all — never a shared placeholder. pageInfo.totalCount is an exact count of the nodes the query can serve, and pageInfo.totalCountIsEstimate is always false, retained for backwards compatibility. Trades still pending on-chain are not included — a withdrawal appears once it reaches the ledger, exactly as in the statement.

The response is of type object.