How to Automate a Trading 212 Portfolio

Key takeaways

• Automating a Trading 212 portfolio means connecting an API key to a tool that keeps a target allocation in line; it does not mean handing over stock picking or market timing.
• Trading 212's API works only with Invest and Stocks ISA accounts and, per its own documentation, is still in beta.
• All three modes, Manual, One-Click Approval and Full Automatic, are available on the main Trading 212 Invest account, because there is no sub-account structure to work around.
• A rebalance trades only the gap between live positions and target weights, and revoking the key or disconnecting sells nothing.
• Rebalance frequency is a setting you choose; regulators and fund managers describe both calendar and threshold approaches, and neither is a return promise.

Trading 212 gives you a fast way to hold a portfolio, but it does not rebalance that portfolio for you. Market moves shift positions away from whatever allocation you started with, and closing that gap by hand means calculating the right trade across every holding and placing it yourself, ideally before the drift gets large enough to matter. Automating that maintenance step is what this article covers: what "automating a Trading 212 portfolio" actually means, what a connection can and cannot do, and the choice you have to make about how much of the process runs without you.

What automation means here

Automating a Trading 212 portfolio does not mean handing over discretionary control to a system that picks stocks or times the market. It means connecting your account to a tool that reads your current positions, compares them against a target allocation built from a published method, and places the trades needed to close the gap on a schedule you set. The target allocation itself, and the method used to build it, come first. Automation is what keeps that allocation from decaying once prices start moving it away from plan.

Acubic is one such tool: an AI portfolio builder with optional broker automation for Trading 212 and eToro. The construction side, how a target allocation gets built in the first place, is covered in full in how Acubic works. This article is about what happens after that allocation exists and you decide whether, and how, to keep it maintained automatically.

How the connection works

A Trading 212 connection runs on an API key you generate yourself inside the Trading 212 app, under Settings, then API (Beta). It is not an OAuth login: you create a separate, revocable credential and hand that to the automation tool rather than sharing your account password. The key is scoped to a defined set of permissions, typically account data, portfolio, metadata, and order read and execute access, with the Pies permissions left off since a rebalancing tool trades positions directly rather than through Trading 212's own basket feature. The moment you revoke the key inside Trading 212, the tool's access ends immediately, independent of anything happening on the tool's side.

Only Invest and Stocks ISA accounts can be connected this way. CFD accounts are outside the scope of the permissions a rebalancing connection uses.

Trading 212 states the boundaries of its API plainly. Its public API documentation says the API "is currently in beta and is under active development" and that it is "enabled and usable only for Invest and Stocks ISA account types". The same page notes that orders "can be executed only in the primary account currency" and that you can optionally restrict an API key to a specific set of IP addresses. An API key, in this context, is a pair of credentials (a key and a secret) that a program sends with every request instead of your login; the broker checks it and applies only the permissions you ticked when you created it.

The one structural fact that matters most

Here is the detail that actually distinguishes automating a Trading 212 portfolio from doing the same thing on some other brokers: a Trading 212 API key is scoped to your whole Invest account, and there is no separate, isolated sub-account to fund. That is different from eToro, where unattended rebalancing requires a distinct eToro sub-account funded apart from your main balance, a constraint that comes from eToro's own account architecture. Trading 212 has no equivalent structure, so every automation mode is available directly on your main account from the outset. We cover that broker-by-broker difference in more depth in how Acubic works with Trading 212.

The three levels of automation

Whatever tool you use, automating a Trading 212 portfolio typically means choosing a point on a spectrum from full manual review to full unattended execution. In Acubic's case, that spectrum has three defined stops:

• Manual: Acubic shows a checklist of the trades needed to bring the portfolio back to target, but it places no orders; you decide whether to place them yourself. Nothing is ever sent to the broker.
• One-Click Approval: on a schedule you set, the system prepares the exact set of trades needed to close the drift and stops there. You review the proposed trades and approve or reject them. This is the default mode, because it keeps a human decision in the loop on every rebalance while removing the manual work of calculating the trades.
• Full Automatic: scheduled rebalances execute without a per-order prompt, behind the same safety guards as one-click approval: one order in flight at a time, conservative position sizing, and a sanity check that halts the run if the calculated trade set looks implausible. Every order is recorded afterward in an audit log regardless of which mode produced it.

Because a Trading 212 connection has no sub-account constraint, you can choose any of the three from day one, on your main account. The detailed mechanics of each mode, and a framework for deciding between them, are in one-click vs full-auto rebalancing.

The automation modes on a Trading 212 connection

Mode (in-app label)	What reaches Trading 212	Your part
Manual	Nothing. Acubic shows a checklist of the trades needed.	Place the trades yourself, if you choose to.
One-Click Approval	The prepared order set, only after you approve it.	Review and approve or reject each rebalance.
Full Automatic	Scheduled rebalance orders, behind the same safety guards.	Set the schedule and review the audit log afterwards.

What a rebalance actually does

A common misconception is that an automated rebalance sells everything and rebuilds the portfolio from scratch. It does not. The system reads your live positions, compares them to the target weights of the strategy you attached to the connection, and trades only the difference. A position already sitting at its target weight is left untouched, and if nothing has drifted meaningfully, nothing trades at all. This distinction, between building a target allocation and defending it against drift over time, is explained further in portfolio optimization vs rebalancing.

Positions you held before connecting, and any amount outside the value you designate as managed, are left alone. Your Trading 212 account does not need to be dedicated entirely to the automated strategy.

What automation does not do

Being clear about the limits matters as much as describing the capability. Automation here reads positions and places equity orders on the schedule and mode you choose. It does not predict short-term price moves, and no part of a construction method built on historical risk relationships depends on doing so; the reasoning behind that is set out in full on the methodology page. It does not touch Trading 212 Pies, and it does not touch CFD accounts. Disconnecting, whether from inside the tool or by revoking the API key directly in Trading 212, does not liquidate anything: every position stays exactly where it is, and the tool simply stops sending future rebalance orders.

Choosing how often it runs

Automation also means picking a rebalance frequency, not just a level of approval. A frequency that is too tight generates unnecessary trades and turnover on drift that would have corrected itself; a frequency that is too loose lets the portfolio sit meaningfully off target for longer than needed. There is no single correct answer here, because it depends on how volatile the selected holdings are and how much drift you are willing to tolerate before it gets addressed. What matters is that the frequency is a setting you choose deliberately, attached to the strategy on your connection, rather than something baked into the tool's behavior that you cannot see or change.

There are two standard ways to set that frequency. The US Securities and Exchange Commission's beginners' guide to asset allocation describes investors who "rebalance their portfolios on a regular time interval, such as every six or twelve months", and an alternative of rebalancing "only when the relative weight of an asset class increases or decreases more than a certain percentage". The second method is called threshold rebalancing: instead of a date, a tolerance band around each target weight triggers the trade.

Large fund managers use the threshold idea too. In a January 2025 note on its target-date funds, Vanguard reported that its research found "a threshold of 200 bps is suitable across vintages" (Vanguard's approach to target-date fund rebalancing). A basis point (bp) is one hundredth of a percentage point, so 200 bps means two percentage points of drift. That finding is about Vanguard's own funds, not a rule for every portfolio, but it shows the trade-off clearly: a band tight enough to control risk and wide enough to avoid needless trading.

What happens when an order does not fill

Brokers reject orders. An instrument can become temporarily unavailable, a market can be closed, a position can fall below a minimum tradable size. A rebalancing connection worth trusting records that outcome rather than hiding it: when Trading 212 rejects an order, the failure is logged against that specific rebalance run together with the reason the broker gave, and the remaining orders in the same run are handled independently rather than the whole run being abandoned. Every order placed, including a rejected one, should be reviewable afterward in an execution history, so you can reconstruct exactly what happened and why. For the underlying API behavior this rests on, see the Trading 212 API: what you can actually build.

Deciding whether to automate at all

Automation earns its place when you already have a target allocation you believe in and the real problem is upkeep: the portfolio drifts, the corrective trade is tedious to work out across many positions by hand, and it is easiest to skip at exactly the moment it would help most. That is a maintenance problem, and a rebalancing connection solves it directly. It is the wrong fit if what you actually want is stock tips, short-term market calls, or a system that claims to time entries and exits, because no automation mode changes what the underlying method is built to do.

If you want to see the construction side first, before connecting anything, start with the AI portfolio builder or read the full method in our guides. For what the Trading 212 connection can and cannot see once it is live, how Acubic works with Trading 212 is the reference, and the about page covers who is behind the product.

If you are still choosing between brokers, eToro vs Trading 212 for automated investing explains why the automation modes differ structurally between the two. If your Trading 212 money is split across several Pies, read how many Trading 212 Pies to run and Trading 212 Pies versus automated rebalancing before deciding what to automate. When you are ready to set it up, the guide to connecting a Trading 212 account step by step covers the API key, the permissions and the first rebalance, and the overview of the Trading 212 portfolio agent summarises the whole integration on one page.

Sources

1. Trading 212 Public API documentation, Trading 212, accessed 12 October 2026.
2. Beginners' Guide to Asset Allocation, Diversification, and Rebalancing, US Securities and Exchange Commission, accessed 12 October 2026.
3. Vanguard's approach to target-date fund rebalancing (23 January 2025), Vanguard, accessed 12 October 2026.