Page History
...
Please refer to Passthru Fields to view across all venues.
Details
Pricing
| Warningnote | ||
|---|---|---|
| ||
GTX supplies separate sessions for the different liquidity types. Liquidity types distinguishes liquidity in it's market data feed according to the following scopes:
For PriceDepth books, GTX can aggregate scope. The consequence of this is rungs will be a mixture of Interest, Firm and LastLook. If you choose not to aggregate scope, Duplicate price level entries will be seen in the PriceDepth book. Fortunately, GTX can supply separate sessions for the different liquidity types, thus providing clean PriceDepth books. Please refer to PassthruFields above and contact MarketFactory Contact for more details. GTX OrderDepth books do not populate |
| Info | ||
|---|---|---|
| ||
For PriceDepth subscriptions, this venue associates the As such, an individual ID will have a much longer lifetime than the subscriber may otherwise expect. For example, an ID associated with the Top of Book Bid will only be deleted in the unlikely scenario that Bid liquidity should be completely removed for that instrument. |
Orders
Pegged Orders
For PegPriceType: MidPricePeg, MarketPeg and PrimaryPeg are supported .If the Limit Price is populated, then the Limit Price will be pegged, otherwise the specified StopPx will be pegged.for PegPriceType.
Please see table below for custom Peg fields:
| Expand | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Marketable
| Note | ||
|---|---|---|
| ||
Clients can consume
This tag is useful for clients to understand if they got
Please contact MarketFactory Delivery team if you need |
Iceberg and Dark Orders
- It is possible to make Iceberg Orders using
HasExtendedFields[1].MaxShow. - To make Dark orders, simply make MaxShow = 0.
- MaxShow is ignored for IOC orders.
Supported TimeInForces
GTX does not take into account the EffectiveTime(168) for ExposureDuration(1629). ExposureDuration starts as soon as the GTX server receives the order regardless of EffectiveTime.
ExposureDuration will override ExpireTime.
Order Modification
If DiscretionOffsetValue(389) is omitted, the value from the original order will be removed i.e. this tag needs to be explicitly specified every time an order is replaced.
Order Modification
Unlike TransactTime: Unlike NewOrderMultilegs, GTX will NOT reject MiltilegOrderCancelReplaceRequest messages that appear to have been delayed, i.e. TransactTime is ignored for MiltilegOrderCancelReplaceRequest.
The following Values may be changed:
OrdTypeTimeInForceEffectiveTime- ExpireTime
ExposureDuration (will override ExpireTime)StopPxMinQtyMaxShowDiscretionOffsetValueLegPriceLegOrderQty: should be the total intended order quantity, including amount already executed for this chain of orders.
BodyPassthruKeys
- AvgPXLimit
- LastLook
- MatchIncrement
- TriggerPriceType
- AveragingInst
- IOCTimeToLive
The following must be the same as the reference order
PegPriceTypePegOffSetValuePegOffsetTypeNoStrategyParameters(entire group)LegSideLegCurrencyLegSettlDateDiscretionOffsetValue