Cloud · FXAPIs beta · MT5 only

Connect FXAPIs to your Cloud workspace

This connector attaches an existing provider account. It does not create a broker account, store a broker password, warm a terminal, change provider mode or purchase anything. Existing connections on other providers stay unchanged.

Read before connecting

Both fx_test_… and fx_live_… keys reach real brokers. A test key is not a simulated market. Start with a broker demo, never an unfunded live account as a substitute.

A TradeJournal Pro Cloud plan and a suitable FXAPIs plan are separate requirements. Review provider fees yourself. The connection check is read-only, not proof that the key permits execution or that a trade will fill.

Connect in one workspace

  1. In the FXAPIs console, connect your own MT5 demo and bring it online. Wait for ready. Keep its provider mode/lifecycle under your control.
  2. Use a key scoped to accounts:read, trading:read, trading:execute and history:read. Account administration, billing, key-management and webhook permissions are not needed here.
  3. Open Cloud → Connect Account → FXAPIs. Enter the provider account UUID and API key only in that secure form, not in Telegram or support messages. Keys are encrypted and bound to the selected account/owner.
  4. Configure Telegram source, exact broker symbol mapping, a fixed total-lot budget and targets on the same Cloud page. The lot budget is shared across targets. Hedging/netting mode must be confirmed; netting consolidates targets.
  5. On the isolated demo, verify an entry, explicit SL/TP changes, partial/full close and the final journal against broker records. Separately test pending placement, expiry, modification and cancellation when your provider plan permits them. Do not enable live trading until these checks pass.

Coverage and limits

  • Market, limit and stop requests use decimal-string volumes/prices and stable idempotency identities. Pending expiry is forwarded explicitly; omitted SL/TP fields stay unchanged and zero/remove commands become the provider’s explicit null removal.
  • A working pending order is not a fill. Partial or unresolved submissions are held for broker review, never retried blindly. Provider UUIDs and broker position tickets are kept separate. Delayed fills bind through provider deal history; missing/ambiguous evidence is not guessed.
  • Provider symbol data supplies volume rules but does not document trade tick size/value. Quote digits are not tick size. Percentage/money risk, manual breakeven and all automatic protection/scale-outs (BE/trailing, TP chain/cascade and automatic partial actions) are unavailable with this connector. Use broker-visible SL/TP; hidden stops are disabled.
  • Historical candles are not documented: this provider cannot supply journal replay bars. Choose another explicitly supported data source. No public or synthetic prices are substituted as broker evidence.
  • Pending reads expose provider-originated working orders, not every pending order placed from an external terminal. Use an isolated demo and avoid mixing external orders while certifying this beta. Provider snapshots may lag; partial/missing history or stale snapshots are withheld.
  • Trade-journal history excludes deposits and other non-trade ledger entries. Trade-linked commissions and fees are retained. Provider-side copy subscriptions, execution waves, webhooks, account creation, warm/cool/restart and billing are outside this connector.
  • Disconnect here removes the local link/key only. It does not close broker positions, disconnect the provider terminal or cancel its subscription. Check those separately at FXAPIs.

Contract reviewed 20 October 2026 using the official FXAPIs documentation and OpenAPI specification. Automated simulations are not broker-demo certification. Trading involves risk.