[Romazes]

Description

Registers the eToro brokerage in Lean core for the plugin Lean.Brokerages.Etoro.

• BrokerageName.Etoro, wired in BrokerageModel.Create and the reverse lookup.

• EtoroBrokerageModel: equity (US stocks and ETFs), crypto and forex; market orders, and the stop loss and the take profit of a position as contingent exit orders.

  • Defaults to AccountType.Cash, so every security starts at leverage 1. An algorithm sets more with SetLeverage, and the plugin sends that leverage with the order.
  • The stop loss and the take profit are Lean orders the entry triggers (Add contingent orders: OCO, OTO, OUO and brackets #9828): a stop market order is the stop loss, a limit order the take profit, both together a bracket where one cancels the other. eToro keeps them on the position and closes it whole, so CanSubmitContingentOrder accepts a market entry that opens a position, exits on the opposite side for the quantity of the entry, and three orders only as a bracket. The exits skip the cross-zero check: they close the position the entry opens, whatever is held now.
  • A short sale or a position with leverage above 1 needs the stop loss. eToro answers 400 without it: "StopLossRate must be provided when Leverage is greater than 1 or for SellShort transactions". The messages tell the algorithm to attach a stop market order.
  • CanUpdateOrder is true for a price change of an exit order, eToro moves the stop loss or the take profit of the position. A quantity change or any other update is refused: eToro has no order update.
  • A crypto stop loss has to be at least 10% away from the price, at submission and at update. eToro keeps every crypto stop loss at least 10% of the margin away and moves a closer one there without an error: live, a BTC stop asked 5% under the fill came back at exactly 10%. The model refuses it first, with "The stop loss of BTCUSD at eToro has to be at least 10% away from the price ...". Lean checks every order of a set before placing any, so refusing the stop refuses the entry with it.
  • A market sell beyond the long holdings is refused as a cross-zero order; eToro closes positions by units.

  What eToro's eligibility endpoint says about the stop loss and the take profit, as percent of the margin (7934 instruments of the demo account, 2026-11-03; at leverage 1 the margin is the price):

  Type	Config, leverages	min SL %	max SL %	min TP %	max TP %
  Crypto, 417 tradable	real long, 1	10 on all	100	0	1000, 10000 on 143 incl. BTC
  ETF, 592	cfd long 1	0, SCHD 10	100	0	1000
  ETF	cfd long 2,5 and short 1,2,5	0, SCHD 10	50	0	1000
  Forex, 108	cfd long 1	0, EURUSD 1	100, 95 on 19 pairs	0	1000, 500 on 28 pairs
  Forex	cfd long 2 to 30 and short 1 to 30	0, EURUSD 1	50	0	1000 or 500
  Stocks, 6135	real long 1	0 on 6039; 20 on 54; 10 on 5	100	0	1000, 500 on 3
  Stocks	cfd long 2,5 and short 1,2,5	0 on most; 20 on 46; 10 on 6	50, 40 on 11	0	1000

  The take profit has no minimum anywhere. The stop loss minimum is flat for crypto, so the model carries it; it is 0 for the other types except EURUSD and about 60 volatile stocks, which only the eligibility of each instrument tells.

  In an algorithm:

  // a long position with a take profit and a stop loss, a bracket: eToro keeps both on the position
  var tickets = BracketOrder(symbol, 5, takeProfitPrice: price * 1.1m, stopLossPrice: price * 0.9m);
  
  // a short sale needs its stop loss: a one triggers other with a stop market order
  var entry = OrderFactory.MarketOrder(symbol, -5);
  var stopLoss = OrderFactory.StopMarketOrder(symbol, 5, price * 1.1m);
  var shortTickets = OneTriggersOtherOrder(entry, [stopLoss]);
  
  // once the entry filled: move the stop loss of the position, or take the take profit off it
  tickets[2].Update(new UpdateOrderFields { StopPrice = price * 0.95m });
  tickets[1].Cancel();

• OrderContingency.AbsoluteQuantities: the distinct absolute quantities of the orders of a set, next to Symbols, Directions and OrderTypes, so a brokerage model can check the quantities of a set from one order.

• EtoroOrderProperties: the order properties type of the brokerage, with no field of its own.

• EtoroFeeModel: crypto pays 1% of the trade value on every buy and sell (eToro US fees page; a live 85.75 USD BTC buy paid 0.86 USD). Stocks, ETFs and forex pay nothing (eToro US: "We charge zero commissions when you buy or sell a stock"; live EURUSD fills paid no fee).

• Messages.EtoroBrokerageModel: the short sale and the leverage texts.

• Launcher/config.json: etoro-api-url, etoro-api-key, etoro-user-key, etoro-demo-environment and the live-etoro environment.

• BrokerageTests.PlaceOrderWaitForStatus: on a timeout, the failure names each order's expected and actual status and its Invalid message.

Related PR(s)

#9828 (contingent orders). Plugin: https://github.com/QuantConnect/Lean.Brokerages.Etoro/pull/5 and https://github.com/QuantConnect/Lean.Brokerages.Etoro/pull/9

Related Issue

N/A

Motivation and Context

The eToro plugin needs its brokerage name, model, order properties and fee model in Lean core, so Lean routes orders to it, refuses what eToro cannot execute before the order leaves the algorithm, and prices fees in backtests. The stop loss eToro requires came as a price in the order properties before, so Lean never knew it as an order and the close eToro placed at the stop reached Lean as an order placed outside Lean. As a contingent exit order Lean knows it, the plugin fills it when eToro closes the position, and the algorithm can move or remove it.

Requires Documentation Change

Yes: an eToro brokerage page (supported assets and order types, the demo environment flag, the cash account default and SetLeverage, the stop loss as a stop market exit order for a short sale and for leverage above 1, the take profit as a limit exit order, a bracket, the price update of an exit).

How Has This Been Tested?

• EtoroBrokerageModelTests (51 cases): supported and unsupported security and order types, the stop loss for a short sale and for leverage above 1 as a contingent stop market order, 13 shapes of a contingent set (stop loss, take profit, bracket, short, leveraged, exits only, same side, half quantity, limit entry, market exit, two stop losses), exits beyond the holdings, a crypto stop loss at 5%, 10% and 20% from the price at submission and a move to 5% and 20% at update, a cross-zero sell, CanUpdateOrder for an exit price and for a quantity, GetFeeModel, the leverage by account type and security type, the cash default.
• EtoroFeeModelTests (6 cases): zero for equity, 1% of the trade value for crypto, including the live 85.75 USD BTC buy.
• Live through the plugin (plugin PR Fix for indicators to support custom data based on TradeBar class #9, demo account): entries with a stop loss, a take profit or a bracket opened with the rates on the eToro position, long and short; eToro's close at the stop loss filled the Lean stop market order (AAPL long and short) and its close at the take profit the Lean limit order (AAPL, BTC); price updates moved the rates on the position and a wrong rate was refused with the position keeping its rate; removals took the take profit and the stop loss off a long position, and eToro kept the stop loss of a short.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>