Stop Logging Trades.
Let Them Log Themselves.

How Auto-Sync works

Your terminal pushes finished trades to My Trader Pro. Nothing pulls from your broker, and no broker password ever leaves your machine — which is exactly why this works with any broker or prop firm rather than a curated list.

Your terminal  ──▶  MTP ingest endpoint  ──▶  your private queue  ──▶  your journal
   (EA/bot)          authenticated by             held safely           pulled in
                     your API key                 until you're          automatically
                                                  next online           while open

Three pieces, and you only ever touch the first two:

• Your API key — generated in the portal under Signals & Sync. It identifies you and nothing else. It can only add trades to your journal; it cannot read your data, and it cannot touch anyone else's account.
• The sender — our MetaTrader Expert Advisor, or any script, bot or automation tool that can send a web request.
• The queue — trades wait server-side until your portal is open, then land in your journal. Your terminal and your browser never need to be online at the same time.

MetaTrader 5 Recommended

The fastest and most complete route, and the one most prop firms support. Works with every MT5 broker and every funded account.

1. Get your key. Portal → Signals & Sync → Generate my Auto-Sync key. Copy it — it looks like mtp_a1b2c3…
2. Install the Expert Advisor. ⬇ Download MTP-AutoSync.mq5. In MT5: File → Open Data Folder → MQL5 → Experts, drop the file in, then in MT5 press F7 or right-click the Navigator and choose Refresh.
3. Allow MT5 to talk to us. Tools → Options → Expert Advisors → tick the checkbox Allow WebRequest for listed URL → add exactly https://mytraderpro.com → press OK.
   This step causes more failed setups than everything else combined. Three things go wrong: the URL is in the list but the checkbox above it is not ticked (it must be); the URL has a trailing slash, a www. or the full /wp-json/... path (use the bare host exactly as shown); or the dialog is closed with the window X instead of OK, which discards it. Also make sure Algo Trading in the toolbar is on (green).
   This is the step people miss. Without it MT5 blocks the connection and the EA logs error 4014.
4. Attach the EA. Drag MTP-AutoSync from the Navigator onto any chart — any symbol, any timeframe, it doesn't matter which. Paste your key into ApiKey. Press OK.
5. Confirm it's live. The chart shows MTP Auto-Sync — active in the corner, and the Experts tab logs armed. Close a trade and it appears in your journal within a minute.

Settings you can change

MetaTrader 4 Supported

MT4 uses a different language (MQL4) but the same idea and the same endpoint. ⬇ Download MTP-AutoSync.mq4 and follow the MT5 steps — the only difference is the folder: File → Open Data Folder → MQL4 → Experts, and the WebRequest permission lives in the same place (if MT4 logs error 4060, that's the WebRequest permission missing).

Same inputs, same behaviour: one EA watches the whole terminal, closed trades push within a second of the close, and LookbackDays back-fills history on the first run.

TradeLocker Supported

TradeLocker runs in the browser and on mobile — it cannot load MetaTrader robots, so there is no EA to drag onto a chart. It connects through a small bridge script instead, which reads your closed trades through TradeLocker's own API and forwards them to your journal. It never places, modifies or closes an order, and your TradeLocker password never leaves your machine — it is sent only to TradeLocker's own login endpoint.

1. Install Python. Get Python 3.11 or newer from python.org/downloads. On Windows, tick "Add python.exe to PATH" on the first screen of the installer — almost every "python isn't recognised" problem traces back to that box. On macOS it is already installed; check with python3 --version.
2. Install the one dependency. Open Command Prompt (Windows) or Terminal (macOS) and run:
   pip install requests  — on macOS use pip3 install requests.
3. Get your MTP key. Portal → 🔔 Signals & Sync → 📋 Copy key. If you have never generated one, press 🔑 Generate my Auto-Sync key first.
   Generating a new key instantly kills the previous one. If a terminal or script is already running with the old key it will start failing — so only generate a new key when you intend to re-paste it everywhere.
4. Find your TradeLocker server name. It is the third field on the TradeLocker sign-in screen, above email and password (your broker gives it to you — it looks like OSP-DEMO or your broker's name). You need it exactly as shown.
5. Download the bridge. ⬇ MTP-TradeLocker-Sync.py — save it somewhere you can find again, e.g. your Documents folder.
6. Fill in the CONFIG block.
   Do not double-click the file to edit it. On Windows, double-clicking a .py file runs it — a black window appears and closes instantly, which looks like the download is broken. It isn't. To edit it: right-click → Open with → Notepad (or VS Code). To run it, use the Command Prompt as in step 7.
   Near the top you will see:

   "mtp_key":     "PASTE_YOUR_MTP_KEY_HERE",
   "tl_email":    "you@example.com",
   "tl_password": "YOUR_TRADELOCKER_PASSWORD",
   "tl_server":   "YOUR_SERVER_NAME",
   "tl_env":      "demo",

   Replace each value between the quotes. Set tl_env to demo or live to match the account you actually trade. Save the file.
7. Run it. In the same Command Prompt / Terminal, change into the folder you saved it in and run:
   python MTP-TradeLocker-Sync.py  — on macOS, python3 MTP-TradeLocker-Sync.py.
   You should see Connected to My Trader Pro. followed by Watching N TradeLocker account(s).
8. Leave it running. It checks every 60 seconds and closed trades appear in your journal automatically. Closing the window stops the sync — nothing is lost, it simply catches up next time you start it.

Prefer not to leave a window open? Run it once on a schedule instead: python MTP-TradeLocker-Sync.py --once does a single pass and exits. Point Windows Task Scheduler or a cron job at that command as often as you like.

If something goes wrong

cTrader Supported

cTrader can't load MetaTrader robots, but it has its own automation engine — cBots — and we ship one ready to go. The MTP cBot watches for closed positions and writes each one to your journal: entry, exit, stop, target, volume and net P&L, marked broker-verified. It only pushes data out; it cannot place, modify or close an order, and your password never leaves cTrader.

1. Download the cBot. ⬇ MTP-cTrader-Sync.cs — one file, ~100 lines, readable top to bottom.
2. Add it to cTrader. Open the Automate tab (the robot icon) → New cBot → select all in the editor and paste the entire file over it → press Build (F6). "Build succeeded" means you're done here.
3. Get your key. Portal → Signals & Sync → copy your personal sync key.
4. Run it. Add the cBot to any one chart (one chart covers the whole account), paste the key into its MTP Sync Key parameter, and press Play. When cTrader asks about permissions, allow them — the cBot needs Full Access to make the HTTPS call to your journal, and that is the only thing it does with it.

If something goes wrong

Any other platform Universal

Auto-Sync is a plain HTTPS endpoint that accepts JSON. Anything that can send a web request can feed your journal.

Endpoint

POST https://mytraderpro.com/wp-json/mtp/v1/ingest
Content-Type: application/json

Authenticate by putting "key" in the body, or by sending the header X-MTP-Key: your_key. Send one trade, or up to 200 in a trades array.

Payload specification

A successful call returns {"ok":true,"accepted":2,"queued":2}. accepted counts genuinely new trades — a duplicate returns 0, which is a success, not an error.

Working examples

curl — test your key in 5 seconds

curl -X POST https://mytraderpro.com/wp-json/mtp/v1/ingest \
  -H "Content-Type: application/json" \
  -d '{
    "key": "mtp_YOUR_KEY_HERE",
    "symbol": "XAUUSD",
    "direction": "buy",
    "lots": 0.10,
    "entry": 3300.40,
    "sl": 3295.00,
    "tp": 3312.00,
    "exit": 3310.20,
    "profit": 98.00,
    "ticket": "123456789",
    "openTime": "2026.08.05 09:15:00",
    "account": "FTMO 100k",
    "source": "manual test"
  }'

Several trades at once

{
  "key": "mtp_YOUR_KEY_HERE",
  "trades": [
    { "ticket": "900001", "symbol": "XAUUSD", "direction": "buy",
      "lots": 0.5, "entry": 3300.4, "sl": 3295, "tp": 3312, "exit": 3310.2 },
    { "ticket": "900002", "symbol": "EURUSD", "direction": "sell",
      "lots": 0.25, "entry": 1.0910, "sl": 1.0935, "exit": 1.0880 }
  ]
}

Python bot

import requests

def log_trade(t):
    requests.post(
        "https://mytraderpro.com/wp-json/mtp/v1/ingest",
        json={"key": "mtp_YOUR_KEY_HERE", **t},
        timeout=10,
    )

log_trade({
    "ticket": str(order.id), "symbol": order.symbol,
    "direction": "buy" if order.is_long else "sell",
    "lots": order.volume, "entry": order.open_price,
    "sl": order.stop_loss, "tp": order.take_profit,
    "exit": order.close_price, "profit": order.pnl,
})

cTrader cBot (C#)

using System.Net.Http;
using System.Text;

private static readonly HttpClient Http = new HttpClient();

protected override void OnStart()
{
    Positions.Closed += OnClosed;
}

private void OnClosed(PositionClosedEventArgs args)
{
    var p = args.Position;
    var json = "{\"key\":\"mtp_YOUR_KEY_HERE\"," +
        "\"ticket\":\"" + p.Id + "\"," +
        "\"symbol\":\"" + p.SymbolName + "\"," +
        "\"direction\":\"" + (p.TradeType == TradeType.Buy ? "buy" : "sell") + "\"," +
        "\"lots\":" + (p.VolumeInUnits / 100000.0) + "," +
        "\"entry\":" + p.EntryPrice + "," +
        "\"exit\":" + (p.ClosePrice ?? 0) + "," +
        "\"sl\":" + (p.StopLoss ?? 0) + "," +
        "\"tp\":" + (p.TakeProfit ?? 0) + "," +
        "\"profit\":" + p.NetProfit + "," +
        "\"source\":\"cTrader\"}";
    Http.PostAsync("https://mytraderpro.com/wp-json/mtp/v1/ingest",
        new StringContent(json, Encoding.UTF8, "application/json"));
}

TradingView alert

Set the alert's webhook URL to the ingest endpoint and put this in the message box. TradingView replaces the placeholders when the alert fires:

{
  "key": "mtp_YOUR_KEY_HERE",
  "symbol": "{{ticker}}",
  "direction": "{{strategy.order.action}}",
  "lots": {{strategy.order.contracts}},
  "entry": {{strategy.order.price}},
  "source": "TradingView"
}

Troubleshooting

Recovering trades that never arrived

If your journal is missing trades your terminal believes it already sent, one button fixes it: Signals & Sync → Re-pull full history.

It does two things in order. First it re-reads anything still held on the server — every claimed trade is retained for seven days precisely so a browser crash or a closed tab never costs you a record. Then it asks your terminal to forget what it thinks it has sent and replay the whole lookback window.

Your terminal must be running with the EA attached when you press it — the replay comes from MetaTrader, not from us. It normally lands within a minute. If you are on a build of the EA older than 2.30, either update it from the portal or simply remove the EA from the chart and drag it back on, which forces the same full replay.

Security — what your key can and cannot do

Your API key is deliberately weak on purpose. It can do exactly one thing:

• ✅ Add trades to your own journal. That's the whole permission.
• ❌ It cannot read your journal, your stats, your accounts or your settings.
• ❌ It cannot reach any other member's data, whatever it claims in the payload.
• ❌ It cannot change your subscription, your password or your account.

If a key ever leaks, the worst anyone can do is post junk trades into your journal, which you can delete. Rotate it in one click: Signals & Sync → New key, which instantly kills the old one. Revoke switches Auto-Sync off entirely.

Treat the key like a door key, not a bank card: don't paste it into screenshots, public Discord channels or shared repos.