Market Data
Public

Retrieves the latest trades that have occurred for a specific instrument within a specified time range. Returns trade details including price, amount, direction, timestamp, and trade ID.

Use the count parameter to limit the number of trades returned, and sorting to control the order (ascending or descending by trade ID). This method is useful for analyzing trading activity over specific time periods.

Note: For spot instruments routed to Coinbase Exchange, this call is not supported. Use Get product trades directly for full trade history.

📖 Related Article: Spot Trading: Deribit and Coinbase-Routed Instruments

Try in API console

get/public/get_last_trades_by_instrument_and_time

Request

  • Base URL
    https://test.deribit.com/api/v2
  • URL
    https://test.deribit.com/api/v2/public/get_last_trades_by_instrument_and_time
  • Auth
    none declared

Query parameters

instrument_namestring required

Unique instrument identifier

Example:BTC-PERPETUAL

Instrument name

start_timestampinteger

The timestamp (milliseconds since the Unix epoch)

Example:1536569522277

Inclusive earliest timestamp (milliseconds since the Unix epoch). Time-based methods require at least one of start_timestamp or end_timestamp.

end_timestampinteger

The timestamp (milliseconds since the Unix epoch)

Example:1536569522277

Inclusive latest timestamp (milliseconds since the Unix epoch). Time-based methods require at least one of start_timestamp or end_timestamp.

countinteger

Number of requested items, default - 10, maximum - 1000

sorting'asc' | 'desc' | 'default'

Result ordering: asc, desc, or the method-specific default.

Response

Success response

jsonrpc'2.0' required

The JSON-RPC version (2.0)

idinteger

The id that was sent in the request

Example response

{
  "result": {
    "trades": [
      {
        "instrument_name": "BTC-PERPETUAL",
        "timestamp": 1517329113791,
        "starbase_timestamp": 1536569522277000000,
        "block_trade_id": "154",
        "block_trade_leg_count": 3
      }
    ]
  }
}

Changes

    • breaking

      the response property /// became nullable for the status

    • info

      the query request parameter end_timestamp became optional

    • info

      the query request parameter start_timestamp became optional

    • info

      added the optional property /// to the response with the status