E8 Markets has updated its TradeLocker help documentation to explicitly allow connections through the platform’s public API, opening a documented integration route for traders using compatible software. The apparent clarification, noticed in a documentation comparison dated October 24, matters to algorithmic traders—but it does not amount to unconditional authorization of every bot, automated strategy or account program sold under the E8 name.
The firm’s current login guide now includes an API connection section, links to technical documentation and warns users that E8’s support team will not write, debug or maintain integrations. Traders remain responsible for configuring and monitoring their own software, including using the correct symbol names for the E8 account type.
Although the help page makes API connectivity clearly permissible in that context, rules governing trading behavior still apply. E8 publishes separate policies for traditional markets, perpetual products and futures challenges, and those rules do not all treat automation the same way. A working API connection is therefore not itself proof that an automated strategy is allowed or payout eligible.
What Did E8 Add to Its TradeLocker Help Article?
The updated E8 Markets TradeLocker login guide includes a section specifically allowing API connections. Previously, the guide concentrated on locating a customer’s login credentials, identifying the broker server and using the TradeLocker desktop or web interface.
A specialist documentation comparison identified the added section on October 24. The record establishes when the change was observed by the tracker; it does not independently establish the exact moment E8 published the permission or its contractual effective date for existing customers.
E8 tells traders to use the official TradeLocker documentation and handle software development and troubleshooting independently. That allocation of responsibility has practical consequences. If an integration submits an unintended order because it used the wrong instrument code or misunderstood an API response, the trader cannot assume E8 will repair the application or cancel the underlying simulated trade.
The guide also reminds ordinary users to select the broker/prop login option and enter E8 in the TradeLocker server field. Those instructions are relevant because a TradeLocker session authenticated against a different environment does not automatically connect to a customer’s E8 accounts.
How Can Traders Use TradeLocker’s API?
The official TradeLocker public API documentation describes a REST interface for requesting market and account information, obtaining order history, and creating, updating or cancelling orders. It uses access tokens issued after authentication, alongside account-specific identifiers and route information.
For a trader, possible integrations include a custom dashboard showing positions and balances, an automated risk monitor or a strategy implementation that sends orders when conditions are met. Whether that strategy is permissible on a particular E8 account is a separate question governed by E8’s trading restrictions.
One easy implementation mistake is symbol naming. E8 says its TradeLocker gold symbol is not necessarily the bare ticker XAUUSD: Raw-spread accounts use XAUUSD.c, while no-commission accounts use XAUUSD+. A program that assumes generic symbol names may retrieve the wrong instrument, receive errors or fail to act when intended.
TradeLocker also distinguishes identifiers such as an account ID, an account number, and instrument route IDs. Certain endpoints require additional headers. Developers must respect the platform’s endpoint-specific rate limits, while E8 applies its own separate restrictions on orders and server requests.
Connecting software should be tested with a non-production account when appropriate. Unexpected errors, reconnections, duplicate order submissions and position-size rounding can all cause a strategy to diverge from the trade plan even without deliberate misconduct by the broker.
Does API Permission Mean All Trading Bots Are Allowed?
No. For Classic Markets and Perpetual Futures, E8’s published trading policy permits Expert Advisors in defined circumstances, while restricting prohibited conduct such as shared strategies across users, unrealistic simulated-market exploitation and certain high-frequency trading patterns.
Its separate Expert Advisor FAQ states that multiple users running the same trading approach may face account termination. That means buying a popular commercial EA and connecting successfully through the API would not necessarily satisfy E8’s uniqueness and compliance expectations.
There is an important product distinction: E8’s futures-specific rulebook explicitly prohibits semi-automated and fully automated trading, including bots and AI tools. The existence of API functionality on another E8-supported platform does not remove that prohibition for customers governed by the Futures program.
General E8 terms also include restrictions on the use of bots and scripts in certain contexts. A customer planning to use an automated system should therefore establish which account’s binding terms apply, rather than infer global permission from a single technical help article. The product-by-product distinction can be especially significant where a firm sells several distinct forms of simulated funding.
As DaveFinances explained in its analysis of prop firms and brokers, the existence of a trading terminal or technical integration does not necessarily mean traders are executing transactions with a regulated broker using their own investment capital. Contractual rewards and account conditions are still central to these products.
What Trading and API Limits Should E8 Users Check?
E8’s order-limit guidance states that most supported symbols have a maximum ticket size of 50 lots and gold has a 20-lot maximum. It also identifies a limit of 100 simultaneously active open positions and pending orders, up to 2,000 server requests daily and up to 2,000 positions per day, subject to the relevant product rules.
Those figures are broker-level restrictions, not a waiver of TradeLocker’s technical rate limits. An algorithm can remain under an order-per-day maximum yet still encounter API throttling if it polls prices or account information too frequently.
For instance, a script updating orders repeatedly in response to small market moves may use server-request allowances faster than a manual trader. If it hits an endpoint limit, the system may fail to modify an intended stop or close. Position monitoring and failure handling therefore deserve as much attention as the entry strategy.
E8’s trading policy also restricts practices judged impractical in real markets and certain forms of cross-account hedging. The firm can assess trading behavior even if each request was technically accepted by TradeLocker. That is why API authentication and trading-rule compliance should be audited separately.
A related issue appears in DaveFinances’ reporting on OFP Funding payout complaints involving suspected automated trading. The allegations in that unrelated case are unproven, but they illustrate why traders often need specific, documented authorization for the tool and strategy they intend to use.
Who Benefits From a Clearly Permitted API Connection?
The immediate beneficiaries may be programmers and traders who previously lacked a clear answer about whether a TradeLocker API session was permitted on E8. The updated FAQ removes ambiguity about the connection itself, while leaving strategy selection and operational reliability to individual users.
It could also reduce time spent on repetitive manual tasks, such as reconciling positions or generating risk reports. However, the public change record does not disclose new order volumes, API adoption, subscription revenue or customer payouts attributable to the updated guidance.
It also does not confirm whether the same permission extends identically to each E8 account size, jurisdiction, evaluation tier or separate platform. E8’s platform eligibility guide says available terminals vary by region and account type. A customer using MT5, MatchTrader or E8 Terminal should not assume the TradeLocker notice governs that different connection.
Traders considering commercial automation should also be cautious with account credentials and software vendors. TradeLocker’s public API authentication uses access tokens; developers should secure the resulting secrets and avoid distributing account logins to third-party scripts that do not need full control.
In another recent prop trading analysis, DaveFinances reconstructed how a compliance ratio could differ from a trader’s intuitive view of performance. Automation adds another layer of data and timing that may need to be explained if an account is reviewed.
The verified change is narrow but meaningful: E8 expressly allows TradeLocker API connections and points developers to technical resources, while refusing support for custom programming and retaining account-specific trading restrictions. The next useful clarification would be an official matrix specifying which automated behaviors are permitted under each E8 product—not merely whether an API connection can be established.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574