This FAQ covers AlgoWay account settings, webhook error emails, TradingView alerts, email-based TradingView delivery, JSON fields, Telegram Copier, webhook editing, MT5 Expert Advisors, platform-specific notes, notifications and common execution errors.
AlgoWay supports signal sources from TradingView, MT5 and cTrader, with plans starting from $7/month for eligible MT5 routes when billed monthly, or $6/month equivalent with $72 paid upfront for one year, plus a 14-day free trial and 22+ supported platforms.
Do not delete the webhook or create a new trial. Open Trade Webhooks (or Telegram Copier for a Telegram route), find the existing connection and click the pencil icon (Edit Webhook). Correct the Account ID or other destination connection fields and click Save Changes.
This updates the existing webhook, keeping its UUID and remaining trial period. For Telegram-specific settings such as the source channel, use the separate gear icon (Configure Copier) instead. A new trial for the same source and destination platform cannot be started once that trial has been used.
They are the same eligible MT5 automation plan with different billing periods. $7/month is the price when you pay each month. $6/month is the effective price when you pay $72 upfront for 12 months ($72 divided by 12). There is no separate $6 monthly payment option.
Other routes and VPS plans may have different prices. Always check the total and billing period shown for your selected product before paying.
For online support, contact AlgoWay Support on Telegram: https://t.me/AlgoWaySupport.
You can also send your question by email to connect@algoway.trade.
Open AlgoWay Settings, find Webhook Error Email Notifications and click Disable Notifications.
You can enable webhook error emails again from the same section at any time.
A TradingView alert can continue sending requests to an existing AlgoWay webhook even after
the AlgoWay subscription for that webhook has expired. Those requests can generate error notifications,
for example 403 - User subscription expired.
To stop the email notifications, open Settings and use Webhook Error Email Notifications >> Disable Notifications. If the TradingView alert is no longer needed, disable that old alert in TradingView as well.
The Metatrader 5 IP Address Restriction section lets you save an IP address and enable IP restriction for MetaTrader 5 access. AlgoWay also displays your current IP address in this section.
Enter the required IP address, enable IP Restriction and click Save.
Open Settings and find Two-Factor Authentication (2FA). Click Enable 2FA to activate it. If 2FA is already active, the same section provides Disable 2FA.
Open Settings, select the required timezone under Update Timezone and click Save.
Use the dedicated guide: How to Set Up Telegram Notifications on AlgoWay.
Open Settings >> Discord Notifications and paste your Discord Webhook URL. Enable Discord Notifications and click Save Settings.
Click Send Test Message to confirm that AlgoWay can deliver notifications to the configured Discord webhook. To stop Discord notifications later, disable Discord Notifications and save the settings again.
Open Settings and click Open Billing. The Billing page contains your payment history and lets you download an invoice PDF for each payment.
If you paid by credit card or PayPal and automatic renewal is active, open the page for the subscribed service - Trade Webhooks, Telegram Copier, MT5 VPS or All-in-One - and click Cancel.
Canceling stops future automatic charges. It does not stop the service immediately. Your service remains active until the Expiration Date shown in your account.
Payments made through Buy Me a Coffee or cryptocurrency are one-time payments for one month and do not create an automatically renewing subscription, so there is nothing to cancel.
Open Settings, scroll to Delete Account and click Delete Account. This permanently deletes your AlgoWay account, webhooks, settings and associated user data. This action cannot be undone.
If you only want to stop future automatic subscription charges, use the Cancel button for the subscribed service instead of deleting your account.
Not always. AlgoWay also has a workflow where TradingView sends a plain-text email alert to a dedicated AlgoWay email address instead of using a TradingView webhook URL.
In Dashboard >> Your Webhooks, AlgoWay displays a shortened Webhook UUID, so the full webhook URL is not shown directly in the table.
Move the mouse over the Webhook UUID. You will see the Click to Copy tooltip. Click the UUID and AlgoWay copies the full webhook URL to your clipboard.
Paste the copied URL into the Webhook URL field in TradingView.
Yes. One AlgoWay webhook URL can receive TradingView alerts for different symbols, and the same URL can be used in multiple TradingView alerts.
For one trading account, one AlgoWay webhook URL is enough. The webhook UID is connected to that trading account.
One regular webhook UID belongs to one trading account. If one TradingView signal must trade on multiple accounts, use AlgoWay Trade Copier / Clone Mode. In that setup, TradingView sends one alert to the main AlgoWay webhook, and AlgoWay copies the same signal to the additional configured webhook routes.
Normal rule: one TradingView webhook URL can be used for many symbols and many TradingView alerts, but one regular webhook UID belongs to one trading account. For multiple accounts, use Trade Copier / Clone Mode.
Symbol Mapping translates the symbol received from the signal source into the symbol
required by your destination broker or trading platform. Open the webhook editor and enter mappings in
FROM:TO format. The value on the left is the incoming symbol; the value on the right is the destination symbol.
For example, XAUUSD:GOLD means that an incoming XAUUSD signal is sent to the destination as
GOLD. MNQ!1:MNQU6 means that an incoming MNQ!1 signal is sent as MNQU6.
Multiple mappings can be entered in the same field and separated by a comma and/or a space, for example:
XAUUSD:GOLD, MNQ!1:MNQU6
Symbol Mapping is optional. Use it when TradingView, Telegram or another signal source uses a symbol name that is different from the symbol expected by the connected broker or platform.
Open the webhook editor and set Enable red news filter to Yes. Set the required Before news, min and After news, min values, then select the red-news categories that should be included in the filter.
Available categories include CPI, PCE, PPI, GDP, Employment, FOMC/FED, Central Banks, Interest Rates, PMI and Retail Sales.
For example, Before news = 30 and After news = 30 applies the filter for 30 minutes before and 30 minutes after a matching selected news event. Set Enable red news filter to No if you do not want the filter for that webhook.
Yes. You can create manual TradingView alerts and send a structured AlgoWay JSON payload.
Open Dashboard >> Webhook Logs and click Test Webhook. This is an execution test, not only a JSON or connection check. AlgoWay sends the test through the same processing route used by normal incoming signals for the selected webhook, so an accepted test can place an actual order on the connected trading account. Use a demo account or a suitably small quantity when testing.
For a TradingView webhook: select the webhook and enter the symbol, quantity and action. You can also add optional Close Side, SL Price, TP Price, Stop Loss, Take Profit, Trailing Pips and Comment values. The JSON Preview shows the payload AlgoWay will send. When you click Send, that JSON is passed to the selected webhook and then to the same destination-platform handler that processes a real TradingView alert. This lets you test the complete route from AlgoWay webhook input to broker or exchange execution without waiting for TradingView to trigger an alert.
For a Telegram webhook: the test form changes to Telegram Signal Text. Paste the raw signal text as it would normally arrive from Telegram. AlgoWay sends that text through the same Telegram AI parser used for real Telegram signals. The parser interprets the trading instruction first, and the parsed result is then passed to the same execution route used by live Telegram signals. This means the Telegram test checks both signal parsing and final trade execution, not only the broker connection.
After sending the test, check the new row in Webhook Logs. The table records the source, platform, webhook, local time, symbol, action, quantity, OrderId and final status. A success status means the request was processed successfully. If the destination platform returns an order identifier, it is shown in the OrderId column. Some successful actions, such as certain position-closing requests, may not return an OrderId.
If execution fails, the Status column shows See error. Click it to open Error Details. AlgoWay displays the actual error returned during processing, for example a minimum-order restriction, invalid symbol, closed market, invalid stops or another platform-specific rejection. The same Webhook Logs page also records normal TradingView and Telegram signals, so it is the first place to check whether a signal reached AlgoWay and what happened to it afterward.
If you test while the normal market is closed, use an instrument that is actually tradable on the
connected account at that time. On weekends this is commonly a supported crypto instrument such as
ETHUSD.
Check the logs in AlgoWay. If the signal reached the system, you should see the call, parsed fields and the final result or error.
The minimum required fields are:
platform_nametickerorder_contractsorder_action{
"platform_name": "metatrader5",
"ticker": "EURUSD",
"order_contracts": "0.10",
"order_action": "buy"
}
AlgoWay supports two models:
sl_price, tp_pricestop_loss, take_profitIf both are present, the absolute price fields take priority.
Yes, but not on every connector.
The public schema uses trailing_pips.
| Connector Status | Platforms |
|---|---|
Supports trailing_pips |
Binance Futures, Bybit Futures, Bitget Futures, Capital.com, DxTrade, Match-Trader |
Ignores trailing_pips |
cTrader, OKX, MEXC, BitMart |
| MT5 handling | MT5 can use JSON trailing and also EA-based trailing logic |
order_action = "flat" mean?
It means close-position logic.
In hedge-style situations you can also use close_side
to close only one side.
{
"platform_name": "metatrader5",
"order_action": "flat",
"ticker": "EURUSD",
"order_contracts": "0.10",
"close_side": "short"
}
modify and breakeven actions?Yes.
modify is used to update an existing position or order, usually SL/TPbreakeven is used to move Stop Loss to entry price{
"platform_name": "okx",
"order_action": "modify",
"ticker": "ETHUSDT",
"comment": "TV#12345",
"stop_loss": "140",
"take_profit": "280"
}
{
"platform_name": "metatrader5",
"order_action": "breakeven",
"ticker": "GBPUSD",
"order_contracts": "0.10"
}
AlgoWay provides MT5 Expert Advisors for routing and execution workflows. The setup covers installation, webhook configuration, required terminal permissions, EA activation and verification through logs.
For the webhook-based MT5 copier/manual workflow, MT5 must allow Expert Advisors and outgoing WebRequests.
Add at least:
https://algoway.co
For some copier routes you also need the destination platform URL in the WebRequest allow-list.
The MT5 EA input expects the webhook UUID.
Do not paste the full https://... address into the input that expects the AlgoWay webhook ID.
Yes. The MT5 EA supports two models:
It also documents EA-side trailing and breakeven settings:
EnableTrailingStopTrailingStepEnableBreakevenBreakevenAfterPipsYes. The MT5 EA includes:
EnableTelegramNotificationsTelegramChatIdTelegramBotTokenThat guide describes Telegram notifications for disconnect / reconnect related events.
Reverse is the default MT5 EA mode.
close_side can be used to close only one sidelong and short are additionally accepted as buy and selllong becomes short, and short becomes longclose_side is used, its side is inverted tooThe cTrader connector supports two primary modes:
No. The cTrader connector ignores trailing_pips.
415 Unsupported Media Type means AlgoWay received your signal, but the content was not in a shape it could read correctly.
The usual causes are:
At minimum, check these fields first:
platform_nametickerorder_contractsorder_action4752 = trading disabled by client/server.
Check this list:
4756 = request rejected by the broker/server.
Common causes:
4014 can indicate two different problems:
https://algoway.co was not whitelisted in MT5 terminal settings10018 = market closed.
Check symbol trading sessions in MT5 specification and make sure you are not sending orders outside the allowed session.
10024 = too many requests.
This means your automation is sending too many order requests in a very short time. Slow down the request rate and check the logs for repeated order attempts.
No. In Manual mode, the size stated in the Telegram signal takes priority. If the signal has no usable size, AlgoWay uses the amount you entered as Default Order Size. For example, with Default Order Size set to 0.10, a signal explicitly specifying 0.30 lots still uses 0.30 lots. If the signal has no lot size, it uses 0.10.
Other size modes, such as crypto Fixed Money and MT5 Money Fixed or Money Risk, have different precedence rules. See the Telegram Copier size mode manual.
A Telegram Copier route follows one Telegram source channel at a time. The 14-day trial provides one trial route for the selected source and destination platform; additional channels need separate copier routes. Trial access for the same source and destination platform can be used only once.
You can change the channel on your existing trial route in Configure Copier without deleting the webhook or resetting its trial period.
Yes. In Automatic mode, AlgoWay can interpret a range such as BUY XAUUSD Entry: 2340-2345 and normalize it to a single entry price, rather than placing orders across the entire range. The resulting order type depends on the signal and execution rules. This is different from Always Market, which ignores the entry price, and Skip Entry Ranges, which ignores signals containing a range.
Open Telegram Copier, click the gear icon (Configure Copier) for your existing route, select the Telegram source channel and click Save Copier. For the destination broker account or credentials, use the pencil icon (Edit Webhook). Keep the existing route to preserve its webhook UUID and any remaining trial period.