All guides

Cloud · New provider · Demo validation required

Connect MetaTrader API 2.0

This connector is for metatraderapi.net, the default provider for new Cloud connections. It is separate from MetaApi and legacy providers: their credentials are not interchangeable. Existing accounts are not moved automatically.

Before connecting

You need an active TradeJournal Pro Cloud plan, your own paid MetaTrader API seat, and a supported MT4/MT5 broker account. Provider fees are separate. This form attaches an existing seat; it does not purchase, create or release seats. Start with a broker demo.

  1. Connect at the provider. Open the MetaTrader API dashboard, choose the correct MT4/MT5 broker server, and finish connecting your own account there. Use the trading password, not the investor password. Review provider pricing and terms yourself.
  2. Copy the account UUID and trading API key. The key starts with mt5api_, including for MT4. Do not use a management key (mt5mgmt_). A trading-enabled account-scoped key is preferable; never share keys in email or chat.
  3. Attach in Cloud Workspace. Open Broker connection & settings → Connect Account → MetaTrader API. Paste the UUID and key and give the account a name. We verify the active synced connection and read MT4/MT5 and demo/live metadata from the provider.
  4. Review routing and risk. Choose this destination in your channel settings. Review symbol mapping, total lot budget, selected TPs, approval mode, breakeven and trailing rules. Connecting does not enable channels or alter their settings.
  5. Prove the lifecycle on demo. Check a market entry, every selected target, pending order, SL/TP modification, breakeven, trailing, partial close, cancel and close. Check the broker and the journal receipt. A saved key, active connection or HTTP 200 response is not proof of a fill or of API trading permission.

What this integration does

REST requests use the provider's account ID and a server-side key encrypted separately for each connection. The connector routes market/pending entries, management commands, account data, symbols, quotes, historical candles and closed-trade reconciliation through the shared Cloud engine. Broker volume units are converted to lots and order acknowledgements must report a successful broker state.

The provider offers WebSocket streaming, but this connector currently uses REST. No streaming speed claim or broker-demo certification is implied. Hidden/virtual SL/TP and cTrader are not supported by this new connector. Use broker-native protection. Broker restrictions and hedging/netting rules still apply.

Key changes, errors and removal

Use Update API key on the account card after rotating a key. We verify the same account before replacing its saved key; account and journal IDs are preserved. A read-only API key cannot trade even if connection verification succeeds.

For subscription, permission or rate-limit errors, check the provider dashboard. Definite broker refusals are shown as failed, not filled. After an uncertain order response or timeout, inspect broker positions before trying again: the order might already exist. We do not automatically retry trade submissions.

A layer command needs a verified originating signal and a stable Telegram message identity. Replaying that event keeps the same provider idempotency key; a new message is a new intention. Cloud access and the execution pause are checked. For accounts with prop-firm, exposure, loss-breaker or hidden-stop guards, layering is withheld: send a new trade signal through the complete entry checks instead. Do not retry an uncertain submission.

Disconnect removes this link and its stored key from TradeJournal Pro. It does not close broker trades, remove your externally connected seat or cancel provider billing. Manage seats and subscriptions directly with MetaTrader API.

Implementation contract reviewed 19 October 2026. Provider documentation: official API documentation index. Trading involves risk. Keep this new route on demo until your own full lifecycle is verified.

Open Cloud connection settings →