Main clusters and core pages.
AlgoWay lets you connect TradingView alerts to Match-Trader through webhook automation. You create a Match-Trader webhook in AlgoWay, enter the broker platform URL, email and password, optionally enter Account ID, use Auto detect to fill Broker ID, and then paste the AlgoWay webhook URL and JSON message into TradingView.
This guide is written for traders searching for TradingView to Match-Trader, TradingView to MatchTrader webhook, Match-Trader automated trading, MatchTrader trading bot, Match-Trader API trading, Match-Trader prop firm automation, and TradingView alerts to Match-Trader broker.
The execution route is:
TradingView alert → AlgoWay webhook → Match-Trader platform connection → Match-Trader order execution
TradingView creates the signal. AlgoWay receives and validates the webhook JSON. Match-Trader receives the final trading command through the platform URL, account credentials, Account ID if required, and Broker ID configured in AlgoWay.
Last updated: 2026-05-12 • Author: AlgoWay
To automate Match-Trader from TradingView, you need:
After setup, a TradingView alert can become a Match-Trader order through AlgoWay.
Match-Trader is widely used by brokers and prop trading firms. Traders often use TradingView for strategy logic, indicators and alerts, while the execution account is hosted on Match-Trader. AlgoWay connects the two through a webhook route.
This is useful when you want to:
AlgoWay does not create a profitable strategy. It automates the execution route after your TradingView strategy, indicator or manual alert sends the command.
Prepare the following:
https://mtr-platform.fundingpips.com, not https://mtr-platform.fundingpips.com/.
Open the AlgoWay dashboard and create a Match-Trader webhook route.
1.
| Field | Recommended value | Purpose |
|---|---|---|
| Source (from) | TradingView | The alert source. |
| Platform (to) | MatchTrader | The execution destination. |
| Promo Code | Optional | Can extend trial access if valid. |
| Quantity Multiplier | Absolute → 1 | Uses incoming JSON quantity directly. |
| Trade Type | Hedge / Dual side or Reverse | Controls how opposite signals and open exposure are handled. |
| URL | Broker platform URL without trailing slash | Defines which Match-Trader broker environment AlgoWay connects to. |
| Your Match-Trader login email | Used for platform authentication. | |
| Password | Your Match-Trader password | Used for platform authentication. |
| Account ID | Optional if you know it | Can help select the exact account when several accounts exist. |
| Broker ID | Auto detect or manual value | Identifies the broker environment. |
The current AlgoWay Match-Trader webhook form includes an Auto detect button next to the Broker ID field. This is now the recommended way to fill Broker ID.
Example broker URL:
https://mtr-platform.fundingpips.com
If the Auto detect button cannot determine Broker ID, use the manual fallback below.
Manual Broker ID retrieval is only needed when Auto detect does not work for your broker environment.
brokerId or BrokerID.Example value in source code:
brokerId: '1'
In this example, Broker ID is:
1
After saving the Match-Trader webhook, open the webhook list and copy the unique AlgoWay webhook URL.
Webhook URL format:
https://algoway.co/your-webhook-uuid
For TradingView strategy alerts, use this JSON in the alert message field:
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_contracts": "{{strategy.order.contracts}}",
"order_action": "{{strategy.market_position}}",
"price": "{{close}}"
}
TradingView replaces the placeholders when the alert fires:
{{ticker}} — current chart ticker;{{strategy.order.contracts}} — strategy order size;{{strategy.market_position}} — current strategy state;{{close}} — close price at alert time.
If you use a manual TradingView condition such as price crossing a level, use fixed values instead of strategy placeholders.
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_contracts": "1",
"order_action": "buy",
"price": "{{close}}"
}
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_contracts": "1",
"order_action": "sell",
"price": "{{close}}"
}
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_action": "flat",
"order_contracts": "1"
}
Supported common values for order_action:
buyselllongshortflatNow create the alert in TradingView.
The Trade Type setting controls how AlgoWay handles existing positions when a new signal arrives.
| Mode | Behavior | Use case |
|---|---|---|
| Hedge / Dual side | Allows separate long-side and short-side behavior when supported by the account. | Strategies that intentionally use both sides. |
| Reverse | Opposite signal can close or replace the current direction depending on route behavior. | One-direction strategies. |
| flat | Close or flatten matching exposure for the symbol. | Exit signals and manual close alerts. |
Full explanation: How AlgoWay handles opposite trading signals.
If your Match-Trader route supports risk fields, you can send Stop Loss and Take Profit in the JSON. Test these fields with small size before live automation.
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_contracts": "{{strategy.order.contracts}}",
"order_action": "{{strategy.market_position}}",
"price": "{{close}}",
"stop_loss": "100",
"take_profit": "200"
}
{
"platform_name": "matchtrader",
"ticker": "{{ticker}}",
"order_contracts": "{{strategy.order.contracts}}",
"order_action": "{{strategy.market_position}}",
"trailing_pips": "50"
}
stop_loss, take_profit and trailing_pips. Units can depend on platform and route settings.
Before using live size, test the route in layers.
If AlgoWay receives the webhook but Match-Trader does not trade, check platform URL, credentials, Account ID, Broker ID, symbol, size, trade mode and platform response.
Check that the broker platform URL is correct and has no trailing slash. If Auto detect still fails, use manual Broker ID fallback from the login page source code.
Use https://mtr-platform.fundingpips.com, not https://mtr-platform.fundingpips.com/.
AlgoWay must authenticate to the correct Match-Trader account. Verify credentials directly on the broker platform before saving the webhook.
Account ID is optional if you do not know it, but some broker environments or multi-account profiles may require the exact account. Enter it if your broker provides it.
TradingView must send valid JSON. Broken commas, missing quotes or plain text can stop the route before Match-Trader receives anything. See: How to fix AlgoWay webhook Error 415.
For this route, platform_name must be matchtrader.
TradingView ticker may not match the Match-Trader broker symbol. Check the exact instrument name in the broker platform.
Check minimum size, step size, leverage, margin and broker instrument rules.
JSON in the message field is not enough. Enable Webhook URL in TradingView Notifications and paste the AlgoWay URL.
You can build your own TradingView-to-Match-Trader connector, but it requires webhook receiving, JSON parsing, broker environment detection, authentication, symbol mapping, trade mode handling, error logging and ongoing maintenance.
AlgoWay gives you a ready route:
This makes AlgoWay a no-code TradingView to Match-Trader webhook connector for traders who want automation without maintaining their own connector infrastructure.
To connect TradingView to Match-Trader with AlgoWay, create a Match-Trader webhook, enter the broker URL, email and password, use Auto detect to fill Broker ID, optionally enter Account ID, copy the AlgoWay webhook URL, and create a TradingView alert with valid Match-Trader JSON.
AlgoWay turns TradingView alerts into Match-Trader webhook automation without forcing you to build and maintain your own connector.