Symbol mapping

Signal sources, TradingView strategies, Telegram bots, REST API scripts, typically use standard exchange symbols: XAUUSD for gold, EURUSD for the euro-dollar pair, BTCUSD for Bitcoin. MT5 brokers, however, frequently use their own naming conventions, adding suffixes, prefixes, or completely renaming instruments. For example, one broker might list gold as XAUUSDm, another as GOLD, and a third as XAUUSD. (with a trailing dot).

Without mapping, the MT5 Expert Advisor attempts to trade a symbol that does not exist in the broker's Market Watch, and the order fails silently. Symbol mapping solves this at the Route level, you configure the translation once, and every signal that passes through that Route has its symbol rewritten before it reaches the EA.

Symbol mapping is implemented as the transform.symbol_mapRoute Step. Add it to a Route's step pipeline and configure the map object, keys are the source-side symbols and values are the broker-side equivalents.

The Step rewrites signal.Symbol before any downstream filter or Target dispatch receives the signal. Symbols not present in the map are left unchanged, so you only need to list the pairs that actually differ.

Step configuration

{
  "type": "transform.symbol_map",
  "enabled": true,
  "config": {
    "map": {
      "GOLD":   "XAUUSD",
      "SILVER": "XAGUSD",
      "OIL":    "USOIL",
      "BTC":    "BTCUSD",
      "DJ30":   "US30"
    }
  }
}

To configure this Step in the dashboard, open the Route, click Add Step, choose transform.symbol_map, and enter your mappings in the JSON editor. Save the Route to apply immediately, no restart required.

The table below lists symbols that commonly differ between signal sources and broker platforms. Always verify the exact symbol name in your broker's MT5 Market Watch, naming is not standardized and varies by broker.