FRAPropHQ
PROVIDER INTEGRATION BRIEF · UPDATED 29 JULY 2026

A read-only control room for prop traders.

FRA Prop HQ is an independent UK founding-beta software product for journalling, account monitoring, trade review and prop-finance tracking. This brief explains the shared NinjaTrader / Tradovate API connection, the permissions requested and the controls around user data.

PRODUCT PURPOSE

One clear record

Users bring prop accounts, fills, fees, payouts, journals and strategy reviews into one dashboard. The product is designed to improve record-keeping and decision review, not to influence or execute trades.

PRIMARY USERS

Individual prop traders

The initial audience is futures prop traders managing evaluation and funded accounts, including supported NinjaTrader / Tradovate-backed accounts from providers such as Apex and Lucid.

COMMERCIAL MODEL

Membership software

Paid membership tiers provide account limits and product features. FRA Prop HQ does not earn commission from trade execution and does not take custody of customer funds.

REQUESTED PROVIDER SCOPE

Strictly monitoring and history

READ-ONLY LIVE PILOT

Data requested

  • Authorised account identifiers and account metadata
  • Balances and account status needed for dashboard reporting
  • Supported order, execution and fill history for journalling
  • Connection and sync status for customer support

Not requested

  • No order placement, modification or cancellation
  • No automated trading or trade copying
  • No signals, recommendations or account management
  • No resale or redistribution of market data
  • No storage of the user's Tradovate password
USER AUTHORISATION FLOW

Provider consent stays in the provider flow

01 · REQUESTUser chooses Connect NinjaTrader / Tradovate

The customer starts from FRA Prop HQ. No trading credentials are requested by the site.

02 · AUTHORISEThe provider handles consent

The NinjaTrader / Tradovate authorisation screen explains and grants the approved read-only connection.

03 · STORETokens remain server-side

Connection tokens are encrypted before storage and are not exposed through the browser-facing API.

04 · CONTROLUser can sync or disconnect

The customer can remove the connection. Existing journal records remain unless account data is deleted.

TECHNICAL CONTROLS

Practical controls, not marketing claims

Server-side secrets

Provider client secrets and private access tokens are kept in Supabase Edge Function secrets or encrypted server-side records, not in the public frontend bundle.

User data separation

Supabase authentication and Row Level Security are used to separate customer records. Service-role operations stay within server functions.

Traceable imports

CSV imports and cloud sync runs are recorded with status and duplicate protection to make support and reconciliation possible.

Disconnect and deletion

The product includes provider disconnect controls and an account deletion route. A support request route exists when self-service deletion cannot complete.

Clear connection status

The interface labels every connection as Demo or Live and shows its current connection and sync status. Live remains a controlled pilot until real authorised account testing is repeatable.

Fallback operation

Tradovate CSV import remains available so the core journal does not depend on an unapproved provider connection.

PARTNER CORE

Working read-only connector

Authentication adapter

The backend uses user-delegated OAuth. Customers authorise on the provider page and FRA Prop HQ receives a restricted token without seeing the trading password.

Raw provider mirror

Accounts, orders, fills, fill pairs, fees, positions, cash balances and cash logs are mirrored in service-only tables. Browser clients cannot query raw payloads.

User account selection

Discovery does not silently import every provider account. The member selects which authorised accounts should appear in FRA Prop HQ.

Reconciliation

Provider balance and realised P&L are compared with imported gross P&L, fees and net P&L. Differences remain visible for review.

Real-time framework

Current syncing uses read-only REST account and completed-trade endpoints. Market-data redistribution and order routing are excluded.

Feature flags

Demo and Live are stored as separate connections. Demo validation has passed; Live is enabled only for controlled real-account testing.

LIVE TEST PLAN

Live pilot test plan

  1. Confirm OAuth authorisation, token renewal and disconnect behaviour against a real prop login.
  2. Test account discovery against founder-owned or expressly authorised accounts.
  3. Reconcile balances, orders, fills, commissions and timestamps against provider reports.
  4. Test evaluation and funded account coverage without implying support for unverified prop firms.
  5. Test disconnect, expired-token, rate-limit and partial-history cases.
  6. Keep the feature private until results are repeatable and support documentation is complete.
CURRENT DEPENDENCIES

Integration status

ComponentStatusNotes
NinjaTrader / Tradovate connectorLIVE PILOTOAuth, encrypted token storage, Demo account discovery, balances, completed trades, duplicate protection and disconnect/reconnect behaviour have passed validation. Live prop-account testing is underway.
Tradovate CSV importAVAILABLEPreview, duplicate protection and import history are included.
Founder NinjaTrader bridgePRIVATETemporary founder-only bridge. It is not a customer requirement or advertised connection method.
Provider review contact

Technical questions, demo access or security follow-up can be sent to the founding-beta support address.

support@fraprophq.com
RISK DISCLOSURE

Futures and forex trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Risk capital is money that can be lost without jeopardizing one's financial security or lifestyle. Only risk capital should be used for trading and only those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of future results.

HYPOTHETICAL PERFORMANCE DISCLAIMER

HYPOTHETICAL PERFORMANCE RESULTS HAVE MANY INHERENT LIMITATIONS, SOME OF WHICH ARE DESCRIBED BELOW. NO REPRESENTATION IS BEING MADE THAT ANY ACCOUNT WILL OR IS LIKELY TO ACHIEVE PROFITS OR LOSSES SIMILAR TO THOSE SHOWN; IN FACT, THERE ARE FREQUENTLY SHARP DIFFERENCES BETWEEN HYPOTHETICAL PERFORMANCE RESULTS AND THE ACTUAL RESULTS SUBSEQUENTLY ACHIEVED BY ANY PARTICULAR TRADING PROGRAM. ONE OF THE LIMITATIONS OF HYPOTHETICAL PERFORMANCE RESULTS IS THAT THEY ARE GENERALLY PREPARED WITH THE BENEFIT OF HINDSIGHT. IN ADDITION, HYPOTHETICAL TRADING DOES NOT INVOLVE FINANCIAL RISK, AND NO HYPOTHETICAL TRADING RECORD CAN COMPLETELY ACCOUNT FOR THE IMPACT OF FINANCIAL RISK OF ACTUAL TRADING. FOR EXAMPLE, THE ABILITY TO WITHSTAND LOSSES OR TO ADHERE TO A PARTICULAR TRADING PROGRAM IN SPITE OF TRADING LOSSES ARE MATERIAL POINTS WHICH CAN ALSO ADVERSELY AFFECT ACTUAL TRADING RESULTS. THERE ARE NUMEROUS OTHER FACTORS RELATED TO THE MARKETS IN GENERAL OR TO THE IMPLEMENTATION OF ANY SPECIFIC TRADING PROGRAM WHICH CANNOT BE FULLY ACCOUNTED FOR IN THE PREPARATION OF HYPOTHETICAL PERFORMANCE RESULTS AND ALL WHICH CAN ADVERSELY AFFECT TRADING RESULTS.