Connections
Server-backed PAPER provider status and owner controls. No integration is simulated or faked.
Keys stay on the server
API keys and secrets must be stored as server-side secrets and used only inside server functions. They are never placed in browser code, client bundles, URLs or local storage. Live trading stays disabled until a broker is connected and you explicitly enable it in Settings.
PAPER execution provider
Live disabledAlpaca is selected automatically when both server secrets are present. Webull remains available as the fallback.
Sign in to run the read-only GET /v2/account health check.
Webull server credentials are not configured.
Provider selection and account details are owner-only.
Broker paper account (owner only)
The terminal is open to everyone without an account, but broker-account settings are visible only to the signed-in owner.
FOREX.com — connection setup
Paper / demo firstLive routing disabledSign in to check the server-side connection state
1 · API access approved
FOREX.com must approve REST API access for this account before any credentials exist.
2 · Credentials configured server-side
Secrets stored in Project Settings → Secrets. Never entered or cached in the browser.
3 · Paper / demo connection verified
Authenticated against the demo host and reading quotes.
4 · Live connection verified
Authenticated against the live host. Order routing still needs explicit enablement.
Owner checklist
- · Request API access from FOREX.com / StoneX support for your live or demo account — it is not enabled by default.
- · Wait for written approval plus the official API documentation and app key.
- · Add FOREXCOM_BASE_URL, FOREXCOM_APP_KEY, FOREXCOM_USERNAME, FOREXCOM_PASSWORD and FOREXCOM_ACCOUNT_ID in Project Settings → Secrets.
- · Verify the paper/demo host first; the terminal stays OFFLINE until real candles arrive.
- · Live order routing is enabled only after an authenticated connection is verified and you turn it on yourself.
Your normal FOREX.com web/app password is never requested by this UI and is never stored in the browser. Review Order → Confirm Trade and the risk locks stay mandatory in every mode, and demo/paper mode keeps working throughout.
Live news engine
Polls every 30sBenzinga Newsfeed is the primary broad-market source when the server secret BENZINGA_API_KEY is present. Without it the app says NOT CONNECTED and keeps using the official public sources — nothing is substituted or simulated.
- Checking sources…
Webull PaperTrade / OpenAPI
Paper / SandboxPriority adapterNot connectedWebull — sign in to check server credentials
Primary integration for the next testing phase. Signed server-side requests to the Webull OpenAPI sandbox host for accounts, balances, positions, snapshots, historical bars and paper-order preview/place. Live-money routing stays disabled in code.
- WEBULL_APP_KEY — stored server-side
- WEBULL_APP_SECRET — stored server-side
- WEBULL_ACCOUNT_ID (optional) — stored server-side
- WEBULL_API_HOST (default api.sandbox.webull.com) — stored server-side
- WEBULL_REGION (default us) — stored server-side
FOREX.com
Not connectedFOREX.com — NEEDS API ACCESS / CREDENTIALS
First real adapter target: FX/metals market data (XAUUSD and majors) plus balances, positions and order submission. Server-side skeleton exists; endpoints are implemented only against the official docs supplied with API access.
- FOREXCOM_BASE_URL — stored server-side
- FOREXCOM_APP_KEY — stored server-side
- FOREXCOM_USERNAME — stored server-side
- FOREXCOM_PASSWORD — stored server-side
- FOREXCOM_ACCOUNT_ID — stored server-side
TradingView Alerts / Webhook
Not connectedNot connected — webhook endpoint + shared secret required
Receive TradingView alert payloads at a server webhook endpoint and feed them into the signal engine.
- Webhook URL (generated server-side) — stored server-side
- Shared secret — stored server-side
MetaTrader-compatible bridge
Not connectedNot connected — bridge URL + terminal token required
Generic MT4/MT5 bridge endpoint for order routing and account state.
- Bridge URL — stored server-side
- Terminal token — stored server-side
Alpaca
Not connectedUse the PAPER execution provider card above for server health and selection.
US equities and crypto, with paper and live endpoints.
- Key ID — stored server-side
- Secret key — stored server-side
- Paper / Live base URL — stored server-side
Interactive Brokers
Not connectedNot connected — gateway session required
Multi-asset access through the Client Portal gateway.
- Gateway URL — stored server-side
- Session token — stored server-side
Market data feed
Not connectedNot connected — provider + API key required
Real OHLCV and streaming quotes to replace the built-in demo generator.
- Provider — stored server-side
- API key — stored server-side
What gets wired later
- · MarketDataProvider — replaces the demo OHLCV generator with real candles and quotes.
- · BrokerAdapter — order placement, account balance and open positions.
- · Webhook endpoint under /api/public/* — receives TradingView alerts with a verified shared secret.
- · Cloud auth + database — owner login and persistent journal, alerts and settings.