cTrader Automation with Webhooks: A Setup Guide

By the TradeAon team · Published 13 July 2026 · Updated 3 August 2026 · 5 min read

While MetaTrader has long dominated the retail forex space, cTrader has gained market share among traders who value its modern interface, advanced order execution, and robust API. This guide breaks down how cTrader automation works, how it differs from a MetaTrader setup, and how TradeAon's cTrader integration routes TradingView webhooks straight into your account over the cTrader Open API — no cBot, no terminal install.

How cTrader Differs from MetaTrader

Before diving into the setup, it is important to understand the fundamental differences in how cTrader handles automation compared to MetaTrader 4 or 5. MetaTrader relies on Expert Advisors (EAs) coded in MQL4 or MQL5, which are proprietary languages. cTrader, conversely, uses 'cBots' which are coded in C#, a widely used, powerful, and modern programming language supported by the Microsoft .NET framework.

This architectural choice makes cTrader inherently more flexible for developers building complex execution algorithms. Furthermore, cTrader’s order execution model is generally considered faster and more transparent, often providing advanced features like native partial scaling, reverse positions, and precise execution times directly within its core API, without requiring complex workarounds often needed in MT4.

How TradeAon Connects to Your cTrader Account

Unlike MetaTrader, cTrader automation on TradeAon doesn't run through anything installed on your terminal. From the dashboard, you choose Add Account → cTrader, and TradeAon redirects you to cTrader's own login page to authorize access — the same OAuth flow you'd use to grant any third-party app access to your account. There is nothing to download, compile, or attach to a chart.

Once authorized, TradeAon's server holds a persistent connection to your account over the cTrader Open API. Instead of TradingView trying (and failing) to talk to cTrader directly, TradingView talks to TradeAon via a webhook, and TradeAon executes the trade straight against your account through that open connection — no intermediate client process to keep running.

That single architectural difference changes the whole operational picture, and it is worth laying the two side by side — not the settings, which are covered further down, but the plain question of what exists where and what can break it:

What does not change is the alert itself. The same JSON you already send for a MetaTrader account works unmodified against a cTrader one: market and pending orders, stop-loss and take-profit levels, and partial closes by percentage are all understood on both sides. In practice that means moving a working strategy across is a matter of pointing it at the other account, not rewriting the alert.

Routing TradingView Webhooks to cTrader

The process of generating the signal from TradingView is entirely platform-agnostic. Whether the final destination is MT4, MT5, or cTrader, the TradingView setup remains identical.

You create an alert in TradingView and paste your unique TradeAon Webhook URL into the notification settings. The message body must contain the standard JSON payload dictating the trade parameters. Because the TradeAon engine acts as a universal translator, it reads this JSON:

{
  "account_number": "xxxxx",
  "symbol": "XAUUSD",
  "action": "BUY",
  "volume": 0.50,
  "secret": "your-secret-here"
}

Once the engine receives this payload, it looks up which cTrader account is linked under that license key. If the account is connected, it formats the order specifically for the cTrader Open API and dispatches it in milliseconds. The secret field is optional — off by default, and only enforced if you've configured one in your account settings; it's separate from the license key already embedded in your webhook URL.

What Carries Over from an MT Setup (And What Doesn't)

If you are migrating an existing automation setup from MetaTrader to cTrader, much of your infrastructure will carry over seamlessly. Your TradingView Pine Script strategies do not need to be rewritten. Your webhook URL and optional secret (if you use one) remain exactly the same. The TradeAon routing logic, including Proportional volume mapping and cross-broker copy trading capabilities, functions identically.

What differs is volume. MetaTrader takes lots as a decimal — 0.10 means a tenth of a lot. The cTrader Open API does not: it takes an integer volume, and the conversion is volume = lots × lotSize, where lotSize comes from the symbol definition the broker sends us and is expressed in cents. So a symbol with a 100,000-unit contract has a lotSize of 10,000,000, and one standard lot is sent as 10,000,000 — not 100,000, which is the mistake most hand-rolled integrations make.

This matters because the wrong assumption fails silently in the direction that costs money: derive the multiplier from minVolume instead of lotSize and you get the right answer on EURUSD, USDJPY, XAUUSD and BTCUSD — whose minimum happens to be exactly 0.01 lot — and the wrong answer on everything else. TradeAon reads lotSize per symbol and does the conversion server-side, so you keep writing lot decimals in your TradingView payload exactly as you do for MetaTrader.

Verifying Your First Automated Trade

Whenever you connect a new account or migrate to a new platform, verifying the execution pipeline on a demo account is mandatory. The process is simple:

First, confirm the account shows as connected on your TradeAon dashboard — the Accounts page reflects live status straight from the Open API connection, so there's no terminal setting to check.

Next, trigger a manual test alert from TradingView using a micro lot size. Watch the TradeAon dashboard event log—you should see the webhook arrive and immediately register as "Executed." Instantly switch to your cTrader terminal and verify that the order was placed with the correct direction, volume, and risk parameters. Once confirmed, your cTrader environment is fully integrated and ready for live, automated trading.