pub struct MarketIfTouchedOrderRejectTransaction {Show 24 fields
pub id: Option<TransactionID>,
pub time: Option<Timestamp>,
pub user_id: Option<i64>,
pub account_id: Option<AccountID>,
pub batch_id: Option<TransactionID>,
pub request_id: Option<RequestID>,
pub type: Option<TransactionType>,
pub instrument: InstrumentName,
pub units: Decimal,
pub price: Decimal,
pub price_bound: Option<Decimal>,
pub time_in_force: TimeInForce,
pub gtd_time: Option<Timestamp>,
pub position_fill: OrderPositionFill,
pub trigger_condition: OrderTriggerCondition,
pub reason: Option<MarketIfTouchedOrderReason>,
pub client_extensions: Option<ClientExtensions>,
pub take_profit_on_fill: Option<TakeProfitDetails>,
pub stop_loss_on_fill: Option<StopLossDetails>,
pub trailing_stop_loss_on_fill: Option<TrailingStopLossDetails>,
pub guaranteed_stop_loss_on_fill: Option<GuaranteedStopLossDetails>,
pub trade_client_extensions: Option<ClientExtensions>,
pub intended_replaces_order_id: Option<OrderID>,
pub reject_reason: Option<TransactionRejectReason>,
}Expand description
A MarketIfTouchedOrderRejectTransaction represents the rejection of the creation of a MarketIfTouched Order.
Fields§
§id: Option<TransactionID>The Transaction’s Identifier.
time: Option<Timestamp>The date/time when the Transaction was created.
user_id: Option<i64>The ID of the user that initiated the creation of the Transaction.
account_id: Option<AccountID>The ID of the Account the Transaction was created for.
batch_id: Option<TransactionID>The ID of the “batch” that the Transaction belongs to. Transactions in the same batch are applied to the Account simultaneously.
request_id: Option<RequestID>The Request ID of the request which generated the transaction.
type: Option<TransactionType>The Type of the Transaction. Always set to “MARKET_IF_TOUCHED_ORDER_REJECT” in a MarketIfTouchedOrderRejectTransaction.
instrument: InstrumentNameThe MarketIfTouched Order’s Instrument.
units: DecimalThe quantity requested to be filled by the MarketIfTouched Order. A positive number of units results in a long Order, and a negative number of units results in a short Order.
price: DecimalThe price threshold specified for the MarketIfTouched Order. The MarketIfTouched Order will only be filled by a market price that crosses this price from the direction of the market price at the time when the Order was created (the initialMarketPrice). Depending on the value of the Order’s price and initialMarketPrice, the MarketIfTouchedOrder will behave like a Limit or a Stop Order.
price_bound: Option<Decimal>The worst market price that may be used to fill this MarketIfTouched Order.
time_in_force: TimeInForceThe time-in-force requested for the MarketIfTouched Order. Restricted to “GTC”, “GFD” and “GTD” for MarketIfTouched Orders.
gtd_time: Option<Timestamp>The date/time when the MarketIfTouched Order will be cancelled if its timeInForce is “GTD”.
position_fill: OrderPositionFillSpecification of how Positions in the Account are modified when the Order is filled.
trigger_condition: OrderTriggerConditionSpecification of which price component should be used when determining if an Order should be triggered and filled. This allows Orders to be triggered based on the bid, ask, mid, default (ask for buy, bid for sell) or inverse (ask for sell, bid for buy) price depending on the desired behaviour. Orders are always filled using their default price component. This feature is only provided through the REST API. Clients who choose to specify a non-default trigger condition will not see it reflected in any of OANDA’s proprietary or partner trading platforms, their transaction history or their account statements. OANDA platforms always assume that an Order’s trigger condition is set to the default value when indicating the distance from an Order’s trigger price, and will always provide the default trigger condition when creating or modifying an Order. A special restriction applies when creating a Guaranteed Stop Loss Order. In this case the TriggerCondition value must either be “DEFAULT”, or the “natural” trigger side “DEFAULT” results in. So for a Guaranteed Stop Loss Order for a long trade valid values are “DEFAULT” and “BID”, and for short trades “DEFAULT” and “ASK” are valid.
reason: Option<MarketIfTouchedOrderReason>The reason that the Market-if-touched Order was initiated
client_extensions: Option<ClientExtensions>Client Extensions to add to the Order (only provided if the Order is being created with client extensions).
take_profit_on_fill: Option<TakeProfitDetails>The specification of the Take Profit Order that should be created for a Trade opened when the Order is filled (if such a Trade is created).
stop_loss_on_fill: Option<StopLossDetails>The specification of the Stop Loss Order that should be created for a Trade opened when the Order is filled (if such a Trade is created).
trailing_stop_loss_on_fill: Option<TrailingStopLossDetails>The specification of the Trailing Stop Loss Order that should be created for a Trade that is opened when the Order is filled (if such a Trade is created).
guaranteed_stop_loss_on_fill: Option<GuaranteedStopLossDetails>The specification of the Guaranteed Stop Loss Order that should be created for a Trade that is opened when the Order is filled (if such a Trade is created).
trade_client_extensions: Option<ClientExtensions>Client Extensions to add to the Trade created when the Order is filled (if such a Trade is created). Do not set, modify, delete tradeClientExtensions if your account is associated with MT4.
intended_replaces_order_id: Option<OrderID>The ID of the Order that this Order was intended to replace (only provided if this Order was intended to replace an existing Order).
reject_reason: Option<TransactionRejectReason>The reason that the Reject Transaction was created