Dear users,
OVHcloud will perform mandatory maintenance from July 14 at 18:30 UTC until July 15 at 08:00 UTC.
During this period, the server may be unavailable for up to 30 minutes.
After access is restored, you must:
1. Connect to your VPS via RDP.
2. Log in to Windows.
3. Start all MetaTrader 5 terminals.
4. Verify that the trading accounts are connected, Expert Advisors are running, and algorithmic trading is enabled.
OVHcloud will perform mandatory maintenance from July 14 at 18:30 UTC until July 15 at 08:00 UTC.
During this period, the server may be unavailable for up to 30 minutes.
After access is restored, you must:
1. Connect to your VPS via RDP.
2. Log in to Windows.
3. Start all MetaTrader 5 terminals.
4. Verify that the trading accounts are connected, Expert Advisors are running, and algorithmic trading is enabled.
https://algoway.trade/blog/automating-prop-firm-eval-tradingview-algoway.html Our latest article for those interested in trading prop companies using tools https://propfirmpinescripts.com/
algoway.trade
Automating a Prop-Firm Eval with Pine Script and AlgoWay
Connect TradingView Pine Script alerts to AlgoWay and automate prop-firm execution through ProjectX, MT5, or Match-Trader.
🚀 Percentage-Based Stop Loss and Take Profit Are Now Available Across All AlgoWay Crypto Exchanges
We have completed the rollout of percentage-based SL/TP calculations across every cryptocurrency exchange supported by AlgoWay.
You can now choose how
✅ As percentages of the current market price
✅ As price-step values using the existing
✅ As exact prices using
Percentage-Based SL and TP
To enable percentage calculations, add:
The signal must also contain at least one of the following parameters:
or:
Example with both Stop Loss and Take Profit:
In this example:
For a BUY signal, Stop Loss is placed below the price and Take Profit above it.
For a SELL signal, Stop Loss is placed above the price and Take Profit below it.
Using Only Stop Loss
This opens a BUY trade with Stop Loss placed 1.5% below the current market price.
Using Only Take Profit
This opens a SELL trade with Take Profit placed 3% below the current market price.
Exact SL and TP Prices
You can still provide exact prices:
Absolute
For example, when both are included:
AlgoWay will use the exact
Existing Pips Mode
To explicitly use the existing price-step calculation, add:
Example:
When
Trailing Stop
Example:
In this signal, Take Profit is calculated as 3%, while the trailing distance remains 100 pips.
Hyperliquid currently does not support a true Trailing Stop. The trade may be executed, but AlgoWay will return an error indicating that trailing protection was not installed.
⚠️ Important
Percentage-based Stop Loss and Take Profit are currently available only for cryptocurrency exchange connections.
This feature does not automatically apply to MetaTrader, cTrader, TradeLocker, Match-Trader, DXtrade, Capital.com, IBKR, or other non-crypto platforms.
A custom implementation for another platform may be possible. Please contact the AlgoWay administrator to discuss compatibility and integration.
🔥 You can now use the same percentage-based risk settings across instruments with completely different prices.
Set the percentage once, and AlgoWay automatically calculates the correct SL and TP prices for BUY and SELL orders on the selected crypto exchange.
We have completed the rollout of percentage-based SL/TP calculations across every cryptocurrency exchange supported by AlgoWay.
You can now choose how
stop_loss and take_profit should be interpreted:✅ As percentages of the current market price
✅ As price-step values using the existing
pips mode✅ As exact prices using
sl_price and tp_pricePercentage-Based SL and TP
To enable percentage calculations, add:
"sltp_type":"percent"
The signal must also contain at least one of the following parameters:
"stop_loss"
or:
"take_profit"
Example with both Stop Loss and Take Profit:
{"platform_name":"bybit","ticker":"BTCUSDT","order_contracts":"0.01","order_action":"buy","sltp_type":"percent","stop_loss":"1","take_profit":"2.5"}In this example:
stop_loss: 1 means that Stop Loss will be placed 1% away from the current market price.take_profit: 2.5 means that Take Profit will be placed 2.5% away from the current market price.For a BUY signal, Stop Loss is placed below the price and Take Profit above it.
For a SELL signal, Stop Loss is placed above the price and Take Profit below it.
Using Only Stop Loss
{"platform_name":"binance","ticker":"ETHUSDT","order_contracts":"0.1","order_action":"buy","sltp_type":"percent","stop_loss":"1.5"}This opens a BUY trade with Stop Loss placed 1.5% below the current market price.
Using Only Take Profit
{"platform_name":"okx","ticker":"BTC-USDT-SWAP","order_contracts":"1","order_action":"sell","sltp_type":"percent","take_profit":"3"}This opens a SELL trade with Take Profit placed 3% below the current market price.
Exact SL and TP Prices
You can still provide exact prices:
{"platform_name":"bybit","ticker":"BTCUSDT","order_contracts":"0.01","order_action":"buy","sl_price":"98000","tp_price":"105000"}Absolute
sl_price and tp_price values always have priority over relative stop_loss and take_profit values.For example, when both are included:
{"sltp_type":"percent","stop_loss":"1","sl_price":"98000"}AlgoWay will use the exact
sl_price of 98000 and ignore the relative stop_loss value.Existing Pips Mode
To explicitly use the existing price-step calculation, add:
"sltp_type":"pips"
Example:
{"platform_name":"binance","ticker":"BTCUSDT","order_contracts":"0.01","order_action":"sell","sltp_type":"pips","stop_loss":"500","take_profit":"1000"}When
sltp_type is not included, AlgoWay continues to use pips by default. All existing alerts therefore remain compatible.Trailing Stop
trailing_pips always remains pip-based and is not affected by sltp_type.Example:
{"platform_name":"bybit","ticker":"ETHUSDT","order_contracts":"0.1","order_action":"buy","sltp_type":"percent","take_profit":"3","trailing_pips":"100"}In this signal, Take Profit is calculated as 3%, while the trailing distance remains 100 pips.
Hyperliquid currently does not support a true Trailing Stop. The trade may be executed, but AlgoWay will return an error indicating that trailing protection was not installed.
⚠️ Important
Percentage-based Stop Loss and Take Profit are currently available only for cryptocurrency exchange connections.
This feature does not automatically apply to MetaTrader, cTrader, TradeLocker, Match-Trader, DXtrade, Capital.com, IBKR, or other non-crypto platforms.
A custom implementation for another platform may be possible. Please contact the AlgoWay administrator to discuss compatibility and integration.
🔥 You can now use the same percentage-based risk settings across instruments with completely different prices.
Set the percentage once, and AlgoWay automatically calculates the correct SL and TP prices for BUY and SELL orders on the selected crypto exchange.
❤1
🚀 AlgoWay now supports leverage control directly from TradingView signals
You can now send the
Example of a real AlgoWay signal for MEXC:
In this example, AlgoWay will open a BTCUSDT position with 5x leverage.
The feature is supported for MEXC, KuCoin Futures, BitMart Futures, Coinbase Futures, and BingX. If
⚠️ This parameter works only with supported crypto exchanges. For other platforms, leverage control depends on the platform API and may require a custom implementation.
You can now send the
leverage parameter directly in the webhook JSON for supported crypto exchanges. This allows a single strategy to use different leverage values for different instruments, market conditions, and trading scenarios — without changing the platform settings in AlgoWay.Example of a real AlgoWay signal for MEXC:
{"platform_name":"mexc","ticker":"BTCUSDT","order_contracts":"0.01","order_action":"buy","leverage":"5"}In this example, AlgoWay will open a BTCUSDT position with 5x leverage.
The feature is supported for MEXC, KuCoin Futures, BitMart Futures, Coinbase Futures, and BingX. If
leverage is not included in the signal, AlgoWay will use the leverage saved in the connected platform settings.⚠️ This parameter works only with supported crypto exchanges. For other platforms, leverage control depends on the platform API and may require a custom implementation.
👍1
⚡️ TradeLocker: Fewer API Requests, Lower Risk of 429 Errors
Today, we introduced an additional optimization for TradeLocker signal processing.
Previously, for every trading signal, AlgoWay requested:
• the list of available instruments;
• the parameters of the selected instrument, including the minimum volume and lot step;
• the list of open positions;
• and only then performed the trading operation.
When several signals arrived at the same time, the number of requests increased quickly. In rare cases, TradeLocker or its Cloudflare protection could return a 429 Too Many Requests error immediately before opening or closing a trade.
We have now implemented a local cache:
✅ the instrument list is stored locally;
✅
✅ all subsequent signals use the locally stored data;
✅ the cache is separated by Demo/Live environment and broker server;
✅ previously saved data can still be used during temporary API issues.
As a result, each regular signal now sends two fewer API requests to TradeLocker.
This significantly reduces the risk of receiving a 429 error when several signals are processed at the same time.
And as an additional bonus, signal processing is now approximately one second faster. 🚀
The update is already live on AlgoWay.
Today, we introduced an additional optimization for TradeLocker signal processing.
Previously, for every trading signal, AlgoWay requested:
• the list of available instruments;
• the parameters of the selected instrument, including the minimum volume and lot step;
• the list of open positions;
• and only then performed the trading operation.
When several signals arrived at the same time, the number of requests increased quickly. In rare cases, TradeLocker or its Cloudflare protection could return a 429 Too Many Requests error immediately before opening or closing a trade.
We have now implemented a local cache:
✅ the instrument list is stored locally;
✅
minLot and lotStep are saved after the first request for a specific instrument;✅ all subsequent signals use the locally stored data;
✅ the cache is separated by Demo/Live environment and broker server;
✅ previously saved data can still be used during temporary API issues.
As a result, each regular signal now sends two fewer API requests to TradeLocker.
This significantly reduces the risk of receiving a 429 error when several signals are processed at the same time.
And as an additional bonus, signal processing is now approximately one second faster. 🚀
The update is already live on AlgoWay.
⚡️ DXTrade: Instrument Search Fixed for Large Symbol Lists
Today, we fixed an issue affecting DXTrade brokers with more than 1,000 available instruments.
Previously, DXTrade returned only the first part of the instrument catalogue. As a result, symbols located further in the list could not be detected, even when they were available on the trading account.
AlgoWay now automatically loads the complete catalogue in multiple batches until all instruments are received.
Because this requires several API requests, we also introduced local caching for each DXTrade provider. After the first complete download, the instrument list is stored locally and reused for subsequent signals.
This allows AlgoWay to support large DXTrade catalogues correctly while making regular signal processing approximately one second faster.
The update is already live on AlgoWay. 🚀
Today, we fixed an issue affecting DXTrade brokers with more than 1,000 available instruments.
Previously, DXTrade returned only the first part of the instrument catalogue. As a result, symbols located further in the list could not be detected, even when they were available on the trading account.
AlgoWay now automatically loads the complete catalogue in multiple batches until all instruments are received.
Because this requires several API requests, we also introduced local caching for each DXTrade provider. After the first complete download, the instrument list is stored locally and reused for subsequent signals.
This allows AlgoWay to support large DXTrade catalogues correctly while making regular signal processing approximately one second faster.
The update is already live on AlgoWay. 🚀
# Important: AlgoWay Support for BitMEX and BitMart Ends September 1, 2026
BitMEX and BitMart have officially announced that they are shutting down their exchange operations.
BitMart will stop all spot, futures, API, and other trading services on August 26, 2026, at 01:00 UTC. The exchange recommends closing all positions and submitting withdrawal requests as soon as possible.
BitMEX will close its exchange on September 23, 2026, at 04:00 UTC. From August 26, users will no longer be able to open new positions, and BitMEX may begin closing remaining positions as part of its shutdown process.
## Action Required
All AlgoWay users connected to BitMEX or BitMart should immediately:
* Close all open positions.
* Cancel all active orders.
* Stop sending new TradingView alerts to these exchanges.
* Withdraw all remaining funds to another exchange or a wallet under their control.
Do not wait until the final exchange shutdown dates. Withdrawals may require additional verification and may take longer as the closure deadlines approach.
## AlgoWay Integration Shutdown
AlgoWay will permanently discontinue BitMEX and BitMart integrations effective September 1, 2026.
After this date, AlgoWay will no longer process trading alerts or execute orders through BitMEX or BitMart. Users must migrate their automation to another supported exchange before the deadline.
Please take action immediately to protect access to your funds and avoid open positions being closed automatically by the exchanges.
BitMEX and BitMart have officially announced that they are shutting down their exchange operations.
BitMart will stop all spot, futures, API, and other trading services on August 26, 2026, at 01:00 UTC. The exchange recommends closing all positions and submitting withdrawal requests as soon as possible.
BitMEX will close its exchange on September 23, 2026, at 04:00 UTC. From August 26, users will no longer be able to open new positions, and BitMEX may begin closing remaining positions as part of its shutdown process.
## Action Required
All AlgoWay users connected to BitMEX or BitMart should immediately:
* Close all open positions.
* Cancel all active orders.
* Stop sending new TradingView alerts to these exchanges.
* Withdraw all remaining funds to another exchange or a wallet under their control.
Do not wait until the final exchange shutdown dates. Withdrawals may require additional verification and may take longer as the closure deadlines approach.
## AlgoWay Integration Shutdown
AlgoWay will permanently discontinue BitMEX and BitMart integrations effective September 1, 2026.
After this date, AlgoWay will no longer process trading alerts or execute orders through BitMEX or BitMart. Users must migrate their automation to another supported exchange before the deadline.
Please take action immediately to protect access to your funds and avoid open positions being closed automatically by the exchanges.
Automate your trading with AlgoWay. Telegram signals and TradingView alerts are turned into real MT5 trades automatically, including entries, Stop Loss, Take Profit, partial exits and full closes. You keep full control over your trading logic and account while AlgoWay executes every command. WWW.ALGOWAY.TRADE
🤝 New AlgoWay Partnership
We have started a partnership with Prop Firm Pine Scripts, a company specializing in Pine Script strategies for TradingView.
If any AlgoWay user needs a ready-made strategy or a custom strategy based on their own trading rules, this is now another option worth considering:
https://propfirmpinescripts.com/
This announcement is not a recommendation or an offer to purchase any particular product. We are simply informing the AlgoWay community about an additional option available to those looking for a strategy they can later automate.
We have started a partnership with Prop Firm Pine Scripts, a company specializing in Pine Script strategies for TradingView.
If any AlgoWay user needs a ready-made strategy or a custom strategy based on their own trading rules, this is now another option worth considering:
https://propfirmpinescripts.com/
This announcement is not a recommendation or an offer to purchase any particular product. We are simply informing the AlgoWay community about an additional option available to those looking for a strategy they can later automate.
Prop Firm Pine Scripts
Pine Script Strategies for Prop Firm Evaluations
Automated Pine Script strategies built to pass FTMO, Apex, Topstep, and MyFundedFutures evaluations. From $24/mo.
🚀 AlgoWay MT5 EA v2.15 is now available
This update improves how Stop Loss and Take Profit levels are handled in MetaTrader 5.
A new SL/TP reference option has been added, allowing levels to be calculated from the actual trade entry price. This can provide more consistent SL/TP distances, especially on instruments with wider spreads.
We have also improved reliability when opening multiple positions in Hedge mode, so each new trade is matched and managed more accurately.
The existing SL/TP behavior remains the default, so current setups will continue working as before. Users who prefer entry-price-based SL/TP calculations can enable the new option in the EA settings.
Version: 2.15 https://algoway.trade/downloads/AlgoWay_WS/MQL5/Experts/AlgoWayWS-MT5.ex5
This update improves how Stop Loss and Take Profit levels are handled in MetaTrader 5.
A new SL/TP reference option has been added, allowing levels to be calculated from the actual trade entry price. This can provide more consistent SL/TP distances, especially on instruments with wider spreads.
We have also improved reliability when opening multiple positions in Hedge mode, so each new trade is matched and managed more accurately.
The existing SL/TP behavior remains the default, so current setups will continue working as before. Users who prefer entry-price-based SL/TP calculations can enable the new option in the EA settings.
Version: 2.15 https://algoway.trade/downloads/AlgoWay_WS/MQL5/Experts/AlgoWayWS-MT5.ex5
❤1