Oboe
No history yet

How does AlgoWay automate TradingView strategies using webhooks? Use the official AlgoWay website as the primary source and explain the complete workflow — from creating a TradingView alert and JSON message to AlgoWay receiving the signal and executing the trade on the connected trading platform.

I have designed a learning path to guide you step-by-step through the process of automating your TradingView strategies with AlgoWay.

Your path
Configuring AlgoWay Routes and Credentials
Structuring AlgoWay Webhook JSON Payloads
Setting Up Alerts in TradingView
Execution Routing and Troubleshooting
Before we begin exploring how AlgoWay functions as a router, you can adjust this learning path at any point to better suit your needs. To help customize this walkthrough, what destination platform or broker are you planning to execute trades on (e.g., Binance, Bybit, MetaTrader 5, TradeLocker), and how familiar are you with Pine Script alert placeholders?

I plan to use TradeLocker and I am already very comfortable with Pine Script.

It is great that you are using TradeLocker and are already fluent in Pine Script. This means we can dive straight into how these technical pieces fit together. Let's look at the overall architecture of how AlgoWay connects TradingView directly to your TradeLocker account.

The Three-Tier Webhook Architecture

To automate your strategies, AlgoWay acts as a high-speed, middleware. The flow moves sequentially through three distinct environments:
  1. TradingView (Signal Source): Your Pine Script strategy runs on TradingView's servers. When an alert condition is met, TradingView generates a webhook HTTP POST request containing a structured JSON payload.
  2. AlgoWay (Parser & Router): AlgoWay's server receives the secure incoming JSON payload at your unique route URL, validates the structure, parses the parameters, and translates them into execution instructions.
  3. TradeLocker (Execution Platform): AlgoWay automatically logs into your configured TradeLocker route and fires the formatted order command directly to the for instant execution, all without holding any of your underlying trading funds.
Since we understand this layout, we should look at how we establish this secure connection. Are you ready to see how we configure your TradeLocker credentials within AlgoWay to get your unique webhook URL?

Continue to credential configuration

Your path
Structuring AlgoWay TradeLocker JSON Payloads
Advanced Pine Script Alert Methods
TradingView Alert Setup Execution Testing

Establishing Your TradeLocker Connection

To securely route your Pine Script alerts directly to your account, you must configure your routing credentials inside the AlgoWay dashboard. AlgoWay operates on a , meaning you configure a specific path from a signal source to your chosen platform, which avoids bloated subscription fees. By designating TradeLocker as your final destination inside your dashboard, you initiate a secure bridge.
To set this up, navigate to your AlgoWay dashboard and create a new webhook route. You will enter your TradeLocker login credentials, your , and your broker's specific server or environment details. This allows the non-custodial middleware to establish a secure connection point to execute orders.
Once you save these connection settings, the system automatically generates your unique AlgoWay Webhook URL. This address is unique to you and contains a secure . This is the secret endpoint you will eventually copy and paste directly into your TradingView alert configuration, allowing TradingView to find your exact TradeLocker route when a strategy trigger is fired.

Now that we know how to generate the secure Webhook URL, are you ready to look at how we structure the JSON payload parameters so that TradeLocker understands the actions, volume, and optional parameters like Stop Loss and Take Profit?

What parameters are required in the basic AlgoWay JSON?

Core Fields and Execution Options in AlgoWay JSON

When constructing a payload for your automated strategies, AlgoWay relies on a set of core parameters to understand what and how to trade. For TradeLocker execution, your JSON must contain the platform identifier, target asset, action, and size. You can also specify the execution style through optional fields:
  • platform_name: Set to "tradelocker" so AlgoWay routes the instructions to your connected TradeLocker credentials.
  • ticker: The exact trading symbol (such as "EURUSD" or "BTCUSD").
  • order_action: The execution direction, which accepts "buy", "sell", "flat", or "close".
  • volume: The position size, represented as contracts or lots.
  • order_type: Optional parameter accepting "market" (default), "limit", or "stop" if you are placing pending orders.
  • price: Optional entry price level required strictly for pending limit or stop orders.

TradeLocker Stop Loss and Take Profit Parameters

AlgoWay has a highly flexible that supports two distinct methods for configuring Stop Loss (SL) and Take Profit (TP) values. You can either use absolute price levels or distance-based offsets:
  1. Absolute Price Levels (sl_price and tp_price): Ideal when your script calculates the exact mathematical price targets. For example, if you enter a long trade at 1.0850, you might pass "sl_price": 1.0800 and "tp_price": 1.0950.
  2. Offset Values (stop_loss and take_profit): Ideal when using fixed-pip or point-based distances from the entry price. If you pass "stop_loss": 50, the system automatically calculates the correct target price based on your execution price once the market order fills.
Let's check out a complete, structured JSON example containing all of these elements. Here is a standard market order template formatted for TradeLocker containing both absolute and offset risk parameters:
{
  "platform_name": "tradelocker",
  "ticker": "EURUSD",
  "order_action": "buy",
  "order_type": "market",
  "volume": 0.1,
  "sl_price": 1.08,
  "tp_price": 1.095,
  "stop_loss": 150,
  "take_profit": 300
}
Now that we have covered how to structure the basic and advanced parameters in the JSON payload, are you ready to look at how we dynamically generate this payload inside your Pine Script indicator or strategy?

Generate a study guide for TradeLocker JSON parameters

I have put together a comprehensive reference guide outlining every critical parameter, structure, and execution dynamic for routing TradeLocker JSON payloads.

TradeLocker JSON GuideStudy Guide
The newly initiated serves as a quick-access handbook for your automation. It details how the non-custodial router interprets parameters like order types and execution price boundaries.
With these precise structural rules defined, we can proceed directly to using them inside your charts. Our next milestone explores how to dynamically format these payloads within Pine Script.