Paper endpoint is a required boundary
The connector rejects a paper request without a configured paper endpoint rather than silently falling through to a live endpoint.
Trading software product
Webull Trading Bot Engine for Signal Routing
A Webull-connected Trading Bot Engine for receiving authenticated strategy signals and recording paper or client-controlled live order workflows through an OpenAPI connection.
Implementation scope
What this product implements
The service creates strategies with hashed API keys, accepts signals only from an active strategy, and stores the original request payload with the recorded order information.
Its configuration defaults to paper mode and checks for a paper endpoint before a paper order is submitted. The same workflow can use live mode only with an explicit allow-live setting, required credentials, and the applicable live endpoint.
The Webull client wrapper resolves an instrument, creates a client order identifier, submits a market-order request through the optional SDK, and records the returned platform identifier when present.
Engineering choices
Clear boundaries in the application design
Configuration is checked before live use
Live operation requires a separate flag plus application credentials and an account identifier in the configuration model.
Access is separated by role
Administrative configuration and strategy-originated signals use different authentication paths, while order history restricts a strategy to its own records.
Validation approach
How the product can be reviewed
- The product’s health, access control, strategy-signal, and order-recording paths can be reviewed as part of an implementation check.
- A test-signal interface supports review of the configured application flow before any separately enabled live operation.
Current boundaries
Important limitations
- The product supports paper and client-controlled live order workflows. Paper mode is the default; live mode needs a separately enabled configuration, valid account credentials, and the applicable live endpoint.
- The product needs valid Webull credentials and a confirmed endpoint for the selected environment before it can make a broker request.
- Real-time order-update handling and region-specific onboarding need to be confirmed for the selected deployment. Paper verification checks software behaviour only and does not predict live results or trading performance.
- Sun Cluster provides software engineering, not investment advice, brokerage, custody, or discretionary trading services.