Truth before breadth

What code can finish—and what still needs someone else.

A connector is not “done” because a logo appears. Production status requires sanctioned access, a complete order lifecycle, reconciliation, and dated evidence. This register names the external dependency for every unfinished promise.

View what works now Service status

4

Need credentials / sandbox

2

Need vendor access

4

Need outside validation

1

Explicitly not promised

execution

DXtrade execution

Needs vendor / broker access

No production connector. DXtrade availability depends on the broker or prop firm exposing API access.

Required next

  1. 1Name a target broker/firm
  2. 2Obtain its sanctioned API access and sandbox
  3. 3Build and certify open/modify/partial-close/close reconciliation

Completion evidence

A sandbox lifecycle test and a named supported broker move this route to beta.

Official access source

execution

Match-Trader execution

Needs vendor / broker access

No production connector. The platform publishes trading APIs, while access and enabled functions remain broker/server specific.

Required next

  1. 1Obtain an approved broker test account
  2. 2Receive Platform API authentication details
  3. 3Certify REST login plus WebSocket lifecycle

Completion evidence

Broker-sanctioned demo credentials and a recorded order lifecycle move this route to beta.

Official access source

execution

NinjaTrader execution

Needs sanctioned credentials

Official REST Trade API and NinjaScript surfaces exist; TradeJournal Pro has not connected or certified one yet.

Required next

  1. 1Choose REST Trade API or local NinjaScript add-on
  2. 2Obtain development/test access
  3. 3Implement futures contract mapping and bracket reconciliation

Completion evidence

Simulation-account order, modify, partial fill, cancel, and close tests move this route to beta.

Official access source

execution

Tradovate execution

Needs sanctioned credentials

Official REST/WebSocket and OAuth paths exist; no TradeJournal Pro connector is deployed.

Required next

  1. 1Register an OAuth application or approved API-key path
  2. 2Obtain demo and market-data access
  3. 3Implement token refresh, orders, positions, fills, and rate limits

Completion evidence

OAuth review plus a demo lifecycle test moves this route to beta.

Official access source

execution

ProjectX Gateway execution

Needs sanctioned credentials

ProjectX publishes a Gateway API, but TradeJournal Pro has no approved user credentials or production connector.

Required next

  1. 1Identify the target ProjectX-powered firm
  2. 2Obtain sanctioned demo credentials
  3. 3Implement 24-hour session renewal, contracts, orders, and reconciliation

Completion evidence

A named firm, sanctioned test account, and recorded full lifecycle move this route to beta.

Official access source

distribution

Windows installer code signing

Needs independent party

CI now blocks every public Desktop release unless both the app and installer have a valid Authenticode signature, then publishes versioned and stable SHA-256 files. The required publisher certificate has not yet been supplied.

Required next

  1. 1Complete publisher identity validation
  2. 2Purchase an appropriate code-signing certificate
  3. 3Sign installer and update binaries in CI
  4. 4Publish signature verification steps

Completion evidence

Windows shows a verified publisher, CI verifies the signature, and both published SHA-256 sidecars match.

distribution

Apple and Google store distribution

Needs independent party

Native wrappers are not described as store-approved until the stores complete review.

Required next

  1. 1Provide developer-account credentials
  2. 2Complete privacy/data-safety disclosures
  3. 3Submit signed builds
  4. 4Resolve store review findings

Completion evidence

A public listing from the relevant official store.

trust

Independent security assessment

Needs independent party

Internal tests and hardening are not an independent audit or penetration test.

Required next

  1. 1Select an external assessor
  2. 2Agree scope covering web, workers, Desktop update path, secret storage, and broker adapters
  3. 3Remediate findings
  4. 4Publish a dated scope/result summary

Completion evidence

A report or attestation issued by the independent assessor, with scope and date.

evidence

Per-broker lifecycle certification

Needs sanctioned credentials

Generic MT4/MT5 paths compile and are tested, but every broker has its own symbols, limits, filling modes, and account rules.

Required next

  1. 1Collect sanctioned demo accounts for priority brokers
  2. 2Run open/modify/partial-close/close test scripts
  3. 3Publish broker + server + account-mode evidence
  4. 4Re-run after material platform changes

Completion evidence

A dated lifecycle receipt for the exact broker/server/account mode.

evidence

Customer reviews and case studies

Needs independent party

No quotes, returns, or identities are invented. Real review widgets remain empty until customers submit reviews.

Required next

  1. 1Invite actual users after support resolution
  2. 2Obtain consent for case studies
  3. 3Show source-linked reviews without editing performance claims

Completion evidence

A review on an independent platform or a consented, attributable case study.

execution

Device-free IBKR execution

Not promised

The shipped IBKR route uses the official local Client Portal Gateway and therefore needs a running, authenticated device/session.

Required next

  1. 1Do not market the local bridge as provider-hosted cloud
  2. 2Evaluate an approved institutional integration only if IBKR grants suitable access

Completion evidence

A separate IBKR-approved server-side integration—not a workaround around Gateway login or 2FA.

Official access source