Capex
Capex does not publish a public, standalone REST or WebSocket API for retail clients. Automation runs through MetaTrader 5, which supports Expert Advisors, and through the proprietary CapexTrader platform, but there is no documented developer portal on the broker's own site.
That matters if automation is central to your strategy. It doesn't mean you can't trade systematically with Capex. It means your automation lives inside MT5 rather than in a custom Python bot talking to a broker endpoint.
What Traders Ask First
Most people who land on this question are trying to solve one of three problems: they want to run an EA someone sold them, they want to code their own strategy in Python, or they want to copy trades automatically. The answers differ.
- Running a purchased Expert Advisor: yes, if you use MT5 and the EA is MT5-compatible.
- Writing your own bot in Python or Node.js against a Capex REST API: no public API documented for retail.
- Copy trading or signal mirroring: available through platform-level tools, not through a developer API.
The practical upshot: treat Capex as an MT5 automation venue, not a developer-first broker. If your whole plan depends on REST endpoints and webhook order placement, this is not the environment for it.
How Automation Works Here
Automation on Capex runs through two doors, and only one of them supports real algorithmic trading.
MT5 is the real automation path. Expert Advisors, custom indicators, and the Strategy Tester are all native. Traders who have written MQL5 code before will feel at home. Those who have not will need to learn it or buy a ready-made EA.
CapexTrader, the proprietary WebTrader, is a manual platform. It doesn't host EAs the way MT5 does. It is smooth for charting and order entry, but it is not where you run a bot.
One nuance worth flagging for Kenyan traders: VPS hosting matters more than most people expect. MT5 EAs need to run 24/5 without your laptop being open. Latency from Nairobi to a broker server in London or New York is not trivial, and a cheap VPS in the wrong region will cost you on fast strategies.
| Automation path | Supported | Best for |
|---|---|---|
| MetaTrader 5 EAs | Yes | Algo strategies, backtesting |
| CapexTrader WebTrader | No EA hosting | Manual trading, charts |
| Public REST API | Not documented | Custom Python/JS bots |
| Copy trading tools | Platform-level | Mirroring signals |
The MT5 Route in Practice
If you're coming to Capex specifically to automate, the MT5 route is what you're buying. And that comes with tradeoffs you should weigh before funding anything.
Account tiers drive what you can actually run. The Essential account, minimum USD 100, spreads from roughly 1.4 pips on GER40. The Original account starts at USD 1,000. The Signature tier opens at USD 25,000.
For an EA running a scalping strategy, spreads at 1.4 pips eat into returns fast. For a swing strategy holding positions for days, that spread barely registers.
Backtesting quality depends on data availability and your broker's server. Running a test on a demo account from your Nairobi connection will not replicate live conditions in London hours. If you're serious about automation, test on a VPS close to the broker's server infrastructure.
What You Won't Get
Being clear about limits saves you time.
There is no documented public API from Capex for retail clients. That rules out building custom dashboards on top of your account, integrating with third-party portfolio trackers via API keys, or hosting webhook-based order systems.
Capex's onboarding situation has changed. Following the merger into the NAGA Group in August 2024, CAPEX.com no longer accepts new clients directly and redirects prospects to NAGA Markets. That changes what "using Capex for automation" means in practice. If you already hold an account, your automation setup continues to function. If you're opening new, the door leads elsewhere.
| Feature | Available | Notes |
|---|---|---|
| MT5 EAs and custom indicators | Yes | Full MQL5 support |
| Strategy Tester backtesting | Yes | Quality depends on tick data |
| Public REST/WebSocket API | No | Not documented for retail |
| API key generation | No | Not offered |
| VPS hosting by broker | Varies | Verify at account setup |
Where the Real Friction Sits
Automation sounds clean on paper. In practice, three things cause most of the pain for Kenyan traders running algos.
Funding and withdrawal friction. Capex supports cards, bank wire, and e-wallets, and the minimum deposit on the Essential account is USD 100. M-Pesa and other local rails were not verified at review. That means your account is likely USD or EUR denominated, and every deposit or withdrawal carries a conversion cost. M-Pesa caps at KES 250,000 per transaction and KES 500,000 daily, so larger transfers need to route through bank wire anyway.
Regulatory positioning. Capex holds no CMA Kenya licence. Its regulatory footprint relevant to this region is an offshore Seychelles FSA licence (SD020). It is a real licence, not an unregulated operation, but it sits outside the CMA framework that governs online forex for Kenyan residents. CMA-licensed brokers must hold KES 50 million in paid-up capital, segregate client funds, cap leverage around 1:400, and submit to audits. Offshore entities are not bound by those requirements, and there is no local recourse pathway if something goes wrong. That is a criterion to weigh, not a reason to panic.
Tax and reporting. Forex and CFD profits are treated as ordinary income for most Kenyan retail traders and taxed on graduated bands up to a 35% top rate. Trading through a company pays 30% corporate rate. If you're running automated strategies that fire hundreds of trades a month, your record-keeping needs to be systematic from day one. KRA expects an annual return declaring worldwide income between January 1 and June 30.
Why Regulated Alternatives Matter Here
Automation amplifies both wins and losses. That is arithmetic, not marketing language. A manual trader making five decisions a day feels the pain of a bad week. An EA running 500 trades a day can compound a bad parameter set into a blown account before you check your phone.
That asymmetry is why regulated brokers matter more for automated traders than for manual ones. Look for platforms with strong oversight from regulators like FCA, CySEC, or ASIC, segregated client funds, transparent execution policies, and an audit trail you can point to if something goes wrong.
If you're a Kenyan trader automating strategies, this is the filter to apply. Not "is there an API," but "if my bot does something unexpected, what protections exist?" The regulated broker's answer is concrete. The offshore answer is often silence.
Building Your First Setup
The workflow that works when a newcomer asks where to start with automation:
Learn one strategy manually first. Run it by hand for 50 trades and record everything.
Pick MT5 as your platform. It is the standard, the documentation is deep, and free resources are everywhere.
Backtest on at least three years of data, not three months. Short windows lie.
Forward test on a demo for 30 days minimum before touching real money.
Start with one EA on one pair, not five EAs on ten pairs. Complexity kills accounts.
Set a hard loss limit in the EA code itself. Not in your head. In the code.
The traders who succeed at automation treat the first month as tuition. The ones who blow up skip step four, every time.
