Get Trades History
Retrieve information about trades/fills. By default, the most recent trades are returned.
- Unless otherwise stated, costs, fees, prices, and volumes are specified with the precision for the asset pair (
pair_decimalsandlot_decimals), not the individual assets’ precision (decimals).
API Key Permissions Required: Orders and trades - Query closed orders & trades
Authorizations
The "API-Key" header should contain your API key.
Authenticated requests should be signed with the "API-Sign" header, using a signature generated with your private key, nonce, encoded payload, and URI path.
Body
Nonce used in construction of API-Sign header
Type of trade
all, any position, closed position, closing position, no position Whether or not to include trades related to position in output
Starting unix timestamp or trade tx ID of results (exclusive)
Ending unix timestamp or trade tx ID of results (inclusive)
Result offset for pagination
If true, does not retrieve count of ledger entries. Request can be noticeably faster for users with many ledger entries as this avoids an extra database query.
Whether or not to consolidate trades by individual taker trades
Whether or not to include related ledger ids for given trade
Note that setting this to true will slow request performance
Optional parameter for viewing xstocks data.
rebased: Display in terms of underlying equity.base: Display in terms of SPV tokens.
rebased, base Asset class of the pair filter.
forex, equity_pair, futures_contract, synthetic_pair, external_pair Filter results to a single trading pair. An unrecognized pair returns EQuery:Unknown asset pair.
Number of trades returned per page (1–100). Values above 100 get clamped to 100.
1 <= x <= 100