Retrieves the latest user trades that have occurred for a specific instrument. Returns trade details including price, amount, direction, timestamp, trade ID, and order ID.
Results can be filtered by sequence number range or timestamp range. Use the count parameter to limit the number of trades returned, and sorting to control the order (ascending or descending by trade ID). Use historical to retrieve historical trade data.
Main accounts may use the subaccount_id parameter to retrieve trade data for a specific subaccount (requires mainaccount scope).
📖 Related Article: Accessing Historical Trades and Orders Using API
Scope: trade:read
Request
- Base URLhttps://test.deribit.com/api/v2
- URLhttps://test.deribit.com/api/v2/private/get_user_trades_by_instrument
- Authnone declared
Query parameters
Unique instrument identifier
Instrument name
Inclusive sequence number of the first trade to return; cannot be combined with start_timestamp.
Inclusive sequence number of the last trade to return; cannot be combined with end_timestamp.
Number of requested items, default - 10, maximum - 1000
The timestamp (milliseconds since the Unix epoch)
Inclusive earliest timestamp (milliseconds since the Unix epoch); cannot be combined with a start_id or start_seq bound.
The timestamp (milliseconds since the Unix epoch)
Inclusive latest timestamp (milliseconds since the Unix epoch).
Determines whether historical trade and order records should be retrieved.
- false (default): Returns recent records: orders for 30 min, trades for 24h.
- true: Fetches historical records, available after a short delay due to indexing. Recent data is not included.
📖 Related Article: Accessing Historical Trades and Orders Using API
Result ordering: asc, desc, or the method-specific default.
Id of a subaccount
Response
Success response
Example response
{
"result": {
"trades": [
{
"instrument_name": "BTC-PERPETUAL",
"timestamp": 1517329113791,
"starbase_timestamp": 1536569522277000000,
"starbase_order_id": 103148386170,
"block_trade_id": "154",
"block_trade_leg_count": 3
}
]
}
}Changes
- breaking
the response property
///became nullable for the status - breaking
the response property
///became nullable for the status - breaking
the response property
///became nullable for the status - breaking
the
///response's property type changed fromstringtobooleanfor status - breaking
the
///response's property type changed fromstringtobooleanfor status
- breaking
- info
added the optional property
///to the response with the status
- info