Skip to content

Interface: AdvTradeGlobalUserTrade ​

Properties ​

PropertyTypeDescription
advanced?"usd" | "implv"Advanced type of user order: "usd" or "implv" (only for options; omitted if not applicable)
amountnumberTrade size. Use base-coin units for spot, options, and linear instruments, including linear perpetuals; use USD for inverse futures and inverse perpetuals.
api?booleantrue if user order was created with API
block_rfq_id?numberID of the Block RFQ - when trade was part of the Block RFQ
block_rfq_quote_id?numberID of the Block RFQ quote - when trade was part of the Block RFQ
block_trade_id?stringBlock trade id - when trade was part of a block trade
block_trade_leg_count?numberBlock trade leg count - when trade was part of a block trade
combo_id?stringOptional field containing combo instrument name if the trade is a combo trade
combo_trade_id?stringOptional field containing combo trade identifier if the trade is a combo trade
contracts?numberTrade size in contract units (optional, may be absent in historical trades)
directionAdvTradeGlobalDirectionTrade direction of the taker
feenumberUser's fee in units of the specified fee_currency
fee_currencystringCurrency, i.e "BTC", "ETH", "USDC"
index_pricenumberIndex Price at the moment of trade
instrument_namestringUnique instrument identifier
isolated?booleanFlag indicating whether the trade belongs to an isolated margin subaccount. Present and true on isolated trades only.
iv?numberOption implied volatility for the price (Option only)
label?stringUser defined label (presented only when previously set for order by user)
legs?any[]Optional field containing leg trades if trade is a combo trade (present when querying for only combo trades and in combo_trades events). Each leg trade has the same fields as a top-level user trade, including starbase_match_id, starbase_order_id, and starbase_timestamp when matched in Starbase, and starbase_client_order_id for orders submitted via Starbase direct access.
liquidation?"M" | "T" | "MT"Optional field (only for trades caused by liquidation): "M" when maker side of trade was under liquidation, "T" when taker side was under liquidation, "MT" when both sides of trade were under liquidation
liquidity?"M" | "T"Describes what was role of users order: "M" when it was maker order, "T" when it was taker order
main_uid?numberUser identifier for the owning main account. Present on isolated trades only.
mark_pricenumberMark Price at the moment of trade
matching_idstringAlways null
mmp?booleantrue if user order is MMP
order_idstringId of the user order (maker or taker), i.e. subscriber's order id that took part in the trade
order_type?"limit" | "market" | "liquidation"Order type: "limit", "market", or "liquidation"
original_order_type?AdvTradeGlobalOriginalOrderTypeOriginal API order type when an order is represented internally as a limit order. For example, Starbase market orders use "limit" as order_type with "market" in this optional field.
post_only?stringtrue if user order is post-only
pricenumberThe price of the trade
profit_loss?numberProfit and loss in base currency.
quote_id?stringQuoteID of the user order (optional, present only for orders placed with private/mass_quote)
quote_set_id?stringQuoteSet of the user order (optional, present only for orders placed with private/mass_quote)
reduce_only?stringtrue if user order is reduce-only
risk_reducing?booleantrue if user order is marked by the platform as a risk reducing order (can apply only to orders placed by PM users)
starbase_client_order_id?stringClient order id of the user's own order (maker or taker side) submitted directly to Starbase via direct access; not returned for orders placed through the Deribit API; for self-trades this is the taker order's client order id
starbase_match_id?numberOptional field containing the Starbase match identifier (present only for trades matched via Starbase)
starbase_order_id?numberRaw Starbase order id of the user's order, in Starbase's own (non currency-prefixed) id namespace (present only for trades matched in Starbase)
starbase_timestamp?numberOptional field: the Starbase causal timestamp of the trade, in nanoseconds since the UNIX epoch (present only for trades matched in Starbase)
stateAdvTradeGlobalOrderStateInUserTradeOrder state: "open", "filled", "rejected", "cancelled", "untriggered" or "archive" (if order was archived)
tick_directionnumberDirection of the "tick" (0 = Plus Tick, 1 = Zero-Plus Tick, 2 = Minus Tick, 3 = Zero-Minus Tick).
timestampnumberThe timestamp of the trade (milliseconds since the UNIX epoch)
trade_allocations?AdvTradeGlobalTradeAllocations[]List of allocations for Block RFQ pre-allocation. Each allocation specifies user_id, amount, and fee for the allocated part of the trade. For broker client allocations, a client_info object will be included.
trade_idstringUnique (per currency) trade identifier
trade_seqnumberThe sequence number of the trade within instrument
underlying_price?numberUnderlying price for implied volatility calculations (Options only)
user_id?numberUser identifier for the account that executed the trade. For isolated trades, this is the subaccount ID.

Built by Siebly. Open source SDKs for exchange APIs.