Journal EA Overview
The Journal EA (Mytradr.ex5) automatically journals your closed trades from MetaTrader 5 to MyTradr.
How It Works
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ MT5 Terminal│ ──scan──▶ Mytradr.ex5 │ ──POST──▶ MyTradr │
│ Deal History│ │ (read-only) │ │ Server │
└─────────────┘ └──────────────┘ └─────────────┘
- The EA runs on a configurable interval inside your MT5 terminal
- It scans the deal history for completed trades since the last sync
- Builds a JSON payload containing all order and deal data
- Sends the payload to the MyTradr server via HTTP POST
- Server processes and stores the data in Postgres
- Trades appear in your journal
Safe to Use
- Read-only — The EA only reads your deal history. It never places, modifies, or closes trades.
- All account types — Works on live, demo, and prop firm accounts.
- No interference — Does not interfere with other EAs, manual trading, or any other activity on your terminal.
Data Captured
Orders
- Ticket, symbol, order type
- Volume, open price, SL, TP
- Timestamps (setup time, done time)
- Current price, close price
Deals
- Deal ticket, linked order ticket
- Deal type, entry direction
- Volume, price
- Commission, swap, profit
- Timestamp
This gives the journal a complete picture of each trade’s lifecycle — from order placement through execution to close.
Local Backup
Before sending data over HTTP, the EA writes a local JSON backup file. If the HTTP request fails, the backup provides a recovery option. Backup files are stored in the MT5 data folder.
Reliability
- Idempotent processing — Re-sending the same data won’t create duplicate trades
- Retry on failure — The EA retries failed syncs on subsequent ticks
- Server-side logging — All received data is logged for audit trail
- Journal ID stamping — Each sync is tagged with the active journal ID from your MyTradr settings