Broker Integration
Lumverro's Broker Integration layer uses standard API protocols, stateless architecture, and a paper-trading verification mode so you confirm the connection before any live order is sent.
Lumverro connects to your broker via their published REST or FIX API — the same protocols the broker makes available to institutional and retail API clients. We do not use screen-scraping, unofficial endpoints, or workarounds that break when the broker updates their platform. Your API credentials are stored encrypted and are used only to submit orders and retrieve account state; Lumverro does not have withdrawal permissions and cannot request fund transfers. The integration is stateless: if the Lumverro service restarts, it reconnects and resumes from the current market state without replaying missed signals, which avoids double-entry risk.
Before any live connection is activated, you run the integration in paper-trading mode for a minimum of five trading sessions. During this period, the bot generates the same order instructions it would send to a live account but routes them to a simulated fill engine instead. You review the paper-trade log alongside your own manual assessment of the same sessions to confirm that connectivity is stable, that orders match your strategy intent, and that the risk controls fire as configured. Only after your written confirmation does the live API key become active. This is not an optional step — it is a required part of every broker integration engagement.
Concrete details on how the connection is built, tested, and maintained.
REST (JSON over HTTPS) and FIX 4.4/5.0 session protocols. If your broker supports either standard, the integration is technically feasible — contact us with your broker's API documentation for a compatibility assessment.
API keys are stored using AES-256 encryption at rest and transmitted over TLS 1.3. Keys grant order-submission and read-only account-state access only. No withdrawal scope is ever requested or accepted.
On service interruption, the integration reconnects within 30 seconds and evaluates current market state fresh. No buffered signals are replayed, eliminating the risk of duplicate order submission after a connectivity gap.
A dedicated monitoring process checks the broker API connection every 60 seconds and sends an alert to your registered contact if latency exceeds 500 ms or if the connection drops — so you are never unaware of an outage.
Send us your broker's API documentation and we will assess compatibility within two business days at no charge.