The Lab

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

Aggressive vs  Resting Orders

Orders may be:

  • Aggressive - These orders are matched against existing Resting orders held in the order book. Once submitted these orders typically cannot be cancelled or modified.
  • Resting - These orders are submitted at price levels away from the prevailing market, i.e.  buying at a price below or selling at a price above the market.

Time In Force

Details of the TimeInForce values supported by Whisperer Enterprise for both categories are provided below.

The time in force instruction may optionally be refined by the specification of order activation and expiry times:

  • Activation - A specific order activation time may be specified via tag 168/EffectiveTime.
  • Expiry - Order expiry may be specified as a specific time via tag 126/ExpireTime, or as a duration via tag 1629/ExposureDuration. The two representations may not be used together. 


NameNatureDescription59/TimeInForce168/EffectiveTime126/ExpireTime1629/ExposureDuration
Immediate Or CancelAggressiveThe Order must be executed immediately, at least in part (Partial fills are allowed), otherwise the Order is cancelled. AKA 'Fill and Kill'.
IOCOptional--
Fill Or KillAggressiveThe Order must be executed immediately, in full (no Partial fills), otherwise the Order is cancelled.FOKOptional--
Good For AuctionRestingThe order is only active when the instrument enters an auction state. At all other times, the order remains inactive.GFAOptionalOptionalOptional
Good For DayRestingThe Order expires automatically on close of the trading day, if it is still unfilled.GFDOptionalOptionalOptional
Good For TimeRestingOrder is active for a specified duration.GFTOptional-Mandatory
Good 'Til DateRestingOrder is active until a specified time.GTDOptionalMandatory-
Good 'Til CanceledRestingThe Order remains active until it is either executed or cancelled. NOTE: Maximum possible duration is one trading week, but is equivalent to DAY for most Venues that reset daily.GTCOptional--
At Market OpenRestingThe order is only active when the instrument market opens. At all other times, the order remains inactive. It is typically entered when the market is in pre-open state.AMOOptional--
At Market CloseRestingThe order is only active when the instrument market closes. At all other times, the order remains inactive.  It is typically entered when the market is in pre-close state.AMCOptional--

Order Types

Standard Order Types

There are three broad categories of order type:

  • Market - these are aggressive orders that are instructions to deal immediately at the best possible price. When buying, a market order will be filled at the currently prevailing Offer price; when selling, a market order will be filled at the currently prevailing Bid price.
  • Limit - these are resting orders visible to the market - hence the existence of Central Limit Order Book (CLOB) ECNs. They are instructions to deal if a market moves to a specific (more favourable) price or better. Limit orders remain open until they are either entirely filled, or the client submits an order cancel request, or the order expires.
  • Stop - these are resting orders that are not visible to the market and will activate once a specified Stop price has been met.

When matched in a CLOB ECN, Limit orders are said to be 'aggressed' by Market orders.

Details of the OrderType values supported by Whisperer Enterprise for all categories are provided below.


NameCategoryDescription 40/OrdType44/Price99/StopPrice210/MaxShow110/MinQty389/DiscretionOffsetValue211/PegOffsetValue




Limit priceStop priceIceberg tip size
Added to Bid or subtracted from Offer limit price to specify the allowed slippage for the order.
Previously QuotedMarketAn order to hit an individual quote. To hit multiple quotes, aka sweeping, the user must submit individual orders from best to worst price.PreviouslyQuotedMandatory---'--
MarketMarketAn instruction to deal immediately at the best possible price (the current rate).Market------
Dark MarketMarketTODOMarket--ZeroOptional--
Market RangeMarketAKA "Market With Protection". A market order with specified slippage.Market----Mandatory-
Market To LimitMarketOrder that starts as a Market order and in the event of a partial fill,  executes any leaves quantity as a Limit order.MarketLimit------
Market If TouchedMarketMarket order will be submitted to market when a specified price is reachedIfTouched-Mandatory----
LimitLimitAKA "Take Profit". An instruction to deal if a market moves to a more favourable level. Where multiple partial fills are allowed, a Volume Weighted Average Price (VWAP) of the total order quantity may be provided as the limit price.LimitMandatory--Optional--
Dark LimitLimitAKA "Hidden Limit", "Ghost".LimitMandatory-ZeroOptional--
Limit To MarketLimitTODOFunariMandatory--Optional--
Limit If TouchedLimitLimit order will be submitted to market when a specified price is reachedIfTouchedMandatoryMandatory-Optional--
IcebergLimitAKA "Reserve". A limit order that has both displayed and hidden
components.
LimitMandatory-Mandatory---
PeggedLimitAn order with an optional offset to the prevailing market rate. The displayed quantity will float with the market up to the limit price of the order.PeggedOptional-Optional--Optional
DiscretionLimitAKA "Limit With Protection". A limit order with specified slippage. The market sees only the limit price.LimitMandatory---Mandatory-
StopStopAKA "Stop Loss". An instruction to deal if a market moves to a less favourable level.Stop-Mandatory----
Trailing StopStopThe Stop Price follows the market by a specified offset.Stop-----Mandatory
Stop LimitStopExecutes an exposure-reducing limit order when market exceeds order's price.StopLimitMandatoryMandatory----
Trailing Stop LimitStopA Stop Limit order where the stop trigger price is at a fixed amount below the market price, based on the user-defined "trailing" amount. The limit order price is also continually recalculated based on the limit offset.StopLimit----MandatoryMandatory


Algo Orders

More exotic variants of the above order types are generically categorised as Algo Orders and typically require the specification of additional Venue-specific custom parameters. These are able to be specified via the TargetStrategy field and the NoStrategyParameters repeating group.

TWAP Orders

  • TWAP
  • Pegged TWAP
  • Adaptive TWAP

Contingent Orders

  • OCO - One Cancels the Other
  • OTO - One Triggers the Other
  • OUO - One Updates the Other
  • OTOOCO - One Triggers OCO


Instead of dedicated or overloaded fields in the Schema, use:

OrdStatus vs ExecType


OrdStatusExecTypeDescription
PendingNewPendingNewVenue acknowledgement of receipt of Order.
NewNewVenue notification of acceptance of Order by it's matching engine.
ReplacedVenue notification of acceptance of a replacement Order by it's matching engine.
PartiallyFilledPendingMatchVenue notification of a potential match. E.g. EBS and Reuters MAPI.
TradeVenue notification of a done trade.
FilledPendingMatchVenue notification of a potential match. E.g. EBS and Reuters MAPI.
TradeVenue notification of a done trade.
PendingCancelPendingCancelVenue acknowledgement of receipt of OrderCancelRequest.
CanceledCanceled

Venue notification of Order cancellation.

CanceledLastLook-
PendingReplacePendingReplaceVenue acknowledgement of receipt of OrderCancelReplaceRequest.
RejectedRejected-
CalculatedCalculatedVenue notification of a Drop-copy STP trade.
ExpiredExpiredVenue notification of the expiry of a Limit Order.
ErrorError-



  • No labels