Dear users,

Today, May 25, 2026, between 13:54 and 14:47 UTC, our infrastructure was affected by a DDoS attack.

During this period, the webhook server was unavailable, which may have caused some service operations to fail or not be processed correctly.

We apologize for the service disruption. Our team is already working on measures to localize and minimize the impact of similar incidents in the future.

Thank you for your understanding.

🔔 AlgoWay EA Update
A new version of AlgoWayWS-MT5 is available — v2.11
In this update:
✅ some bugs have been fixed
✅ some internal logic has been changed
✅ added the ability to limit the number of trades in one direction
Update file is available here:
https://algoway.trade/downloads/AlgoWay_WS/MQL5/Experts/AlgoWayWS-MT5.ex5

🚀 AlgoWay Red News Filter is now live
We have launched the AlgoWay Red News Filter — a new protection layer for automated trading signals.
Now you can automatically block webhook signals during high-impact economic events such as CPI, PCE, GDP, Employment, FOMC/FED, interest rate decisions, and other red news categories.
You can configure:
✅ enable or disable the filter for each webhook
✅ block signals before a red news event
✅ keep blocking signals after the event
✅ select specific red news categories
✅ protect TradingView, Telegram signals, AI parsing, MT5, crypto exchange, and prop firm workflows
This feature is especially useful for traders who use automation and need better control around news-based volatility.
📘 Full guide:
https://algoway.trade/blog/algoway-red-news-filter-guide.html

Urgent Notice!
PayPal payments are temporarily unavailable due to a PayPal processing issue.

You can still renew your service using Crypto or Buy Me a Coffee. Your service access will not be interrupted while we process alternative payments.

Urgent Payment Update
Direct PayPal payments are temporarily unavailable due to a PayPal processing issue.
We have already added a new payment option: Pay with Credit Card.
Through this checkout, you can subscribe using a bank card, and depending on availability, you may also see PayPal or Link as payment options.
Available payment methods now:
Credit Card / PayPal / Link through the new checkout
Crypto
Buy Me a Coffee as a backup option
Important: if your PayPal renewal date is coming up, PayPal may automatically cancel your subscription during this period. Please keep an eye on your PayPal subscription status and account activity.
On our side, we are adding 2 extra days of access for affected accounts, so you have enough time to pay through an alternative method without losing access to the service.
This is a temporary situation. We are monitoring payments and will assist manually if any payment needs to be checked.

Tonight, after the UTC trading day ends and the planned webhook server restart is completed, a new webhook feature will become available: Symbol Mapping.

This feature allows you to replace an incoming trading symbol with the symbol required by your destination platform.

Format:

FROM

Example:

XAUUSD:GOLD, NAS100:US100, BTCUSDT.P:BTCUSDT

The left side is the symbol received by the webhook.
The right side is the symbol that will be sent to the trading platform.

The field is optional. When it is empty, nothing changes. When no matching incoming symbol is found, the signal continues to work as before. Replacement is applied only on an exact incoming symbol match.

Finally, IBKR is live in AlgoWay Connector.

Production-ready now:
• Stocks: use .STK
• CFDs: use .CFD

Examples: AAPL.STK, MSFT.STK, MSFT.CFD, XAUUSD.CFD.

Important: do not send plain symbols like AAPL, MSFT or XAUUSD. IBKR can resolve them to the wrong instrument/contract, so the suffix is required.

Supported via AlgoWay JSON:
market orders, limit orders, SL/TP, trailing, reverse, flat/close, opposite and inverse logic. AlgoWay waits for Filled before returning success and tracks state by account + contract id.

IBKR session warning: logging in with the same username through TWS, IBKR Gateway, Mobile, Client Portal or web forms can take over the session. During that time AlgoWay trading may be disabled and return a 401 session error. After the other session is closed, the watchdog reconnects automatically.

Futures, options and forex/cash will be added later based on real user requests.

🚀 Telegram Signal Copier update
We have updated the Telegram Signal Copier in AlgoWay.
Now you can test Telegram signals directly from the AlgoWay dashboard before using them in real copying.
Paste the signal text, and AlgoWay will show:
✅ what was parsed from the Telegram signal
✅ the final JSON payload
✅ the broker / platform response
✅ errors if something cannot be executed
What’s new:
🔹 Telegram signal testing from the dashboard
🔹 Entry range handling
Example: Entry: 2.308 - 2.280
🔹 Multiple Take Profit support
🔹 Split Size Between TPs mode
🔹 Separate default trade size by symbol
Example:
BTCUSD:0.01, EURUSD:0.02, USDCAD:0.1
This is especially useful for crypto, metals, indices, and Forex, because one default trade size does not work well for every instrument.
How size logic works:
If the Telegram signal includes a trade size, AlgoWay uses the size from the signal.
If no size is included, AlgoWay uses the default size configured for that specific symbol.
If the symbol has multiple Take Profit levels, AlgoWay can split the position size between them.
We also improved error handling.
The test window now shows not only what AlgoWay understood from the signal, but also the real broker or platform response after sending it.
Telegram Signal Copier is now much closer to a real working automation tool, not just forwarding text into a webhook.

We’ve updated the AlgoWay user dashboard.

After login, users now see a new product Store, making it easier to choose what they want to connect or buy:

* Trade Webhooks - webhook access for TradingView, MetaTrader 5, and cTrader
* MT5 Private VPS - dedicated VPS service for running MetaTrader 5
* Telegram Signal Copier - automation for Telegram trading signals

Trade Webhooks and Telegram Copier are now separated into different sections, so each service can be managed from its own page without mixing different workflows.

The update is already live:
https://algoway.trade/login

⚠️ cTrader O-API authorization issue
Some users may see this error when connecting cTrader O-API:
HTTP 429 Too Many Requests
Too Many Attempts
The error appears after clicking Allow access, during the token request on the cTrader side. In this case, AlgoWay cannot receive the refresh token, so the webhook cannot be saved or updated correctly.
We have contacted cTrader support, and they said they will look into this issue.
For now, please do not click Get Token from cTrader repeatedly. Repeated attempts may trigger or extend the temporary limit.
When cTrader provides an update or fix, we will post it here.

New free strategy in the AlgoWay showcase
RSI Strategy [AlgoWay Edition]
https://www.tradingview.com/script/bnM2Hmsf-RSI-Strategy-AlgoWay-Edition/
This is a simple RSI-based DCA strategy adapted for AlgoWay webhook execution routes.
Important warning: this strategy is not for beginners.
We do not recommend it to traders who do not understand day trading timing, cannot wait days or even a week for a valid signal, or expect every position to close quickly. In some market conditions, a position may stay open for weeks or even close to a month.
We also do not recommend it to anyone who does not understand pyramiding, martingale-style sizing, averaging orders, and DCA risk.
Use it only for testing, research, and with proper risk control.

🚀 BitMEX Trading Module Update

We have added full BitMEX support for order execution and risk management.

What’s new:

✅ Market and Limit order execution
✅ Stop Loss and Take Profit by exact price
✅ Stop Loss and Take Profit by pips
✅ Protective Stop-Loss orders
✅ Take-Profit trigger orders
✅ Trailing Stop in pips
✅ Automatic price and quantity normalization
✅ Flat cleanup: cancels all pending entry, SL, TP, and trailing orders, and closes the open position

BitMEX trading is now safer, more precise, and more convenient for automated trading.

🔔 AlgoWay Notifications Are Now Available on Discord!
Previously, alerts and trading operation notifications were available through Telegram. You can now send them directly to your Discord channels as well.
How to enable Discord notifications:
In Discord, open Channel Settings → Integrations → Webhooks, create a webhook, and copy its URL.
In AlgoWay, go to Settings → Discord Notifications, paste the Webhook URL, enable Discord Notifications, click Save Settings, and use Send Test Message to verify the connection.

A new Entry Order Mode option has been added to the Telegram Copier settings.
Automatic keeps the current behavior: if the signal contains an entry price, a limit order is created.
Always Market ignores the entry price and opens the trade as a market order while preserving the Stop Loss, Take Profit, and position size.

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.

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/

🚀 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 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_price
Percentage-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.

🚀 AlgoWay now supports leverage control directly from TradingView signals
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.