Routing BigQuant Signals to a Broker Through a Trading Terminal

Summary

The document describes a proposed workflow for using BigQuant to generate planned orders and a separate brokerage terminal to place trades when the account is held outside the broker supported for direct live trading. It retrieves planned orders through BigQuant’s API, separates buy and sell signals, and sends orders through the terminal’s command interface. A second example monitors live quotes and compares price with a moving average derived from five-minute bars, using a threshold crossing as a timing signal.

This is an implementation sketch, not a validated trading system. The article’s order-handling example contains apparent inconsistencies, including a sell-time loop that iterates over buys and calls the buy function, while the signal rules and order sizing are not fully explained. It provides no backtest or live performance evidence and does not discuss safeguards such as duplicate-order prevention, API-key handling, or execution failures. The moving-average example illustrates a possible timing condition but gives no basis for its predictive value.

Key ideas

• The proposed workflow retrieves strategy orders from BigQuant and submits them through a separate trading terminal.
• It divides planned orders into buy and sell lists before execution.
• A sample timing rule compares live price with a moving average from intraday bars.
• The examples contain implementation gaps and provide no evidence of trading performance.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.