Opening — Who this guide is for and what it solves
You are an active retail trader, quant, or developer who wants to automate trades on eToro while managing risk. You want practical, runnable options. You want setup steps you can follow in 10–60 minutes. You want limits, numbers, and checklists to avoid surprises.
This guide explains the practical ways to automate on eToro. It covers the official API (how to get keys and authenticate), agent platforms (Tori and AI agents), built-in copy automation (CopyTrader and Smart Portfolios), and DIY browser bots (Selenium). You will get step-by-step checklists. You will see the common commands and files used in quick proofs-of-concept. You will get concrete numbers for testing capacity and throttling. You will also get an operational decision tree to pick the right approach for your skill level and capital.
Follow the checklists. Test on the demo account. Limit requests and position sizes. Log everything for at least 90 days. Use the final decision tree to pick one path in under 15 minutes.
Quick Answer / TL;DR — Get started fast
If you want full programmatic control → request the Official eToro API keys (2 key types). Test on the $100,000 demo first.
If you want autopilot via other people → use CopyTrader or Smart Portfolios (real-time replication; copying has no extra fee).
If you want AI-assisted signals and orchestration → use Tori or agent platforms (connect via API user keys; integrate OpenClaw, Hermes, or Claude-based agents).
If you want a quick proof-of-concept or scraping-only automation → run a Selenium-based bot (install 2 pip packages; run 1 python command). Expect fragility and possible compliance risk.
1. What “eToro automated trading” means and 3 main approaches
Automated trading on eToro means executing or copying trades without manual clicks. Do this using programmatic interfaces or platform features. Use automation to place orders, monitor positions, and replicate other traders.
Approach 1: Official API-driven automation. Use programmatic REST calls to place orders, read positions, and manage accounts. Use 2 key types (public read-only and user/trading keys). Expect 1–3 auth flows and token refresh cycles.
Approach 2: Platform-native automation. Use CopyTrader and Smart Portfolios. CopyTrader replicates trades in real time at 1:1 replication latency under normal liquidity. Smart Portfolios bundle assets into a managed basket with rebalancing schedules, typically 1–90 days depending on the product.
Approach 3: DIY browser bots and scrapers. Use Selenium to script the web UI. Install 2 pip packages and run 1 python command. Expect fragility: plan for 1–3 breakages per month.
Test scale and duration numbers here. Always use the $100,000 demo account first. Run a minimum 30-trade test or at least 14 calendar days before any live deployment. For risk validation, run at least 100 demo trades or 30 calendar days for statistically meaningful P&L samples.
Trade types supported vary by approach. Official API supports spot, CFD, and crypto positions for eligible accounts. Copy operations replicate whatever the copied trader executes, including margin and CFD. Selenium bots mirror whatever the web UI supports, but execution details vary by instrument and liquidity.
Watch out for operational limits. Avoid automation that sends more than 100 requests per minute to the platform. Engineer a safe cap of 60 requests per minute per account while testing. Avoid placing many micro-orders; 50 orders of $10 each can multiply spreads and fees.
Best for: Programmatic control, predictable latency, and full data access.
Skip if: You need a turn-key, no-code solution with no technical overhead.
Key points:
– Key points: Use the $100,000 demo for all tests and simulations before live trades.
– Key points: Run 30 trades or 14 days minimum for a quick validity check.
– Key points: Cap request bursts at 60 requests/min per account as a starting rate.
– Key points: Backtest or paper-trade for 100 trades or 30 days for statistical confidence.
– Key points: Expect 1–3 UI breakages per month if you choose Selenium automation.
Watch out for: placing many small orders and triggering spread or fee amplification.
2. Official eToro API — 2 key types and 3-step setup
Use the Official eToro API when you need full programmatic control. Place market and limit orders, read positions, and manage account settings. Use the API for server-to-server execution, user-consent flows, or automated agents.
Follow a tight 3-step setup:
1) Request developer access and enable API in your Account Settings. Expect 1 approval step and an email confirmation within 24–72 hours in typical cases.
2) Create a user key for live trading (scoped to trading) and a public key for read-only access. Keep at least 1 read-only key and 1 trading key per environment.
3) Store keys securely in a secrets manager. Rotate keys every 90 days and revoke compromised keys immediately.
Integration notes and numbers:
– Use standard REST endpoints and send auth headers with each request.
– Plan for at least 2–3 authentication flows: server-to-server with client credentials, user-consent OAuth, and token refresh using refresh tokens.
– Test all code on the $100,000 demo account. Run at least 100 demo orders as a smoke test.
Concrete limits and engineering caps:
– Limit bursts: use a soft cap of 60 requests/min per account, and a hard cap of 100 requests/min as a safety boundary.
– Use retry logic: set exponential backoff starting at 200 ms, doubling to 1.6 s over 5 retries.
– Log every API call with a timestamp and latency. Keep logs for 90 days.
Security and operational tips:
– Do not expose user keys in client-side code. Avoid embedding keys in web apps or mobile apps.
– Rotate keys every 90 days and enforce a maximum 5 concurrent keys per account.
– Audit logs: retain API call logs for 90 days, with 1-minute resolution snapshots for critical trading hours.
Best for: Developers who need full control and can manage keys and servers.
Skip if: You want a no-code, managed solution or cannot secure API keys.
Key points:
– Key points: Use 2 key types — public (read-only) and user (trading).
– Key points: Rotate keys every 90 days and keep at most 5 concurrent keys.
– Key points: Cap requests at 60/min as a safe default; avoid >100/min bursts.
– Key points: Test on $100,000 demo; run 100 demo trades before live.
– Key points: Implement token refresh and 2–3 auth flows for resilience.
Watch out for: exposing user/trading keys in browser code or mobile apps.
3. CopyTrader & Smart Portfolios — automatic copying with 0 extra fee and $100K demo
Use CopyTrader to replicate another investor’s trades automatically. Use Smart Portfolios to buy a managed basket that rebalances on a schedule. Both let you automate without code.
Setup steps with concrete numbers:
– Find a trader or portfolio. Screen at least 10 candidates and shortlist 3.
– Set your allocation. Allocate a fixed dollar amount (e.g., $500) or a percent (e.g., 5%) of your portfolio.
– Configure stop-loss and max drawdown. Use a hard stop of 5%–10% per copied allocation, and a daily loss limit of 3% for each copy.
– Enable automatic copying. Start in the $100,000 demo. Run for at least 14 days or 30 trades on demo to validate behavior.
Concrete features and numbers:
– Copying has no additional copying fee. Expect 0 extra charge for the copying feature itself.
– Replication latency is near real-time. Expect 1–5 seconds in liquid markets; expect up to 5–60 seconds in thin markets.
– Use allocation sizing: recommended allocation per copied trader is 10%–30% of total capital for diversified exposure.
Use cases and capacity:
– Passive investors: allocate 10%–30% of capital to copied traders as a starting point.
– Diversification: copy 3–5 traders to spread risk; monitor each at least once per day.
– Smart Portfolios: pick portfolios with rebalancing cycles of 30, 60, or 90 days depending on strategy.
Pitfalls and attention items:
– Copying replicates all trades, including leveraged or CFD positions. If a copied trader uses 5x leverage, your copy will reflect that exposure proportionally.
– Historical performance is not a guarantee. Use at least 90 days of historical stats and a sample of 100 trades if available.
Best for: Investors who want hands-off exposure and zero code.
Skip if: You require customized execution logic or strict position sizing at sub-account level.
Key points:
– Key points: Copying has 0 extra platform fee for the feature itself.
– Key points: Use $100,000 demo for behavior tests; run 14–30 days or 30–100 trades.
– Key points: Start with allocation 10%–30% of capital per copied trader.
– Key points: Expect replication latency of 1–60 seconds based on liquidity.
– Key points: Copy 3–5 traders to diversify; monitor daily.
Watch out for: copying leveraged trades that amplify losses beyond your risk tolerance.
4. Agentic platforms and Tori — connect 3 agent types using API keys
Agentic automation uses AI agents to generate signals and, optionally, execute via the eToro API. Agents analyze market data and send trade instructions. You may pick separate signal and execution agents.
Agent list and integration times:
– Common agents used in community demos include OpenClaw, Hermes, and Claude-based agents. Count 3 typical agents you can test quickly.
– Expect an initial integration time of 10–30 minutes to supply API keys, set scopes, and select trading limits.
Integration steps with numbers:
1) Generate an API user key with trading scopes. Limit the key to specific scopes and set expiry to 90 days.
2) Configure the agent with the key. Set execution limits: max position size per trade (e.g., $1,000), max daily loss (e.g., $200), and max open positions (e.g., 5).
3) Run in demo mode for 100–200 trades or 7–14 days to validate signals.
Operational specifics:
– Agents commonly produce signals every 1–60 minutes depending on the strategy. Choose 1-minute signals for scalping, 15–60 minute cadence for swing strategies.
– Use rate-limited calls to avoid hitting request caps: design agents to target 30 requests/min per account.
– Include a kill-switch and emergency stop. Implement a single API endpoint or UI button that shuts off execution with 1 click.
Best use cases:
– Traders who want signal orchestration without building full execution stacks.
– Quant teams testing models quickly: run 100 demo trades in 7 days for rapid feedback.
Best for: Those who want AI signals and managed execution without writing the low-level execution code.
Skip if: You require full auditability of model decisions or cannot tolerate black-box decisioning.
Key points:
– Key points: Test agents on demo with 100–200 trades or 7–14 days.
– Key points: Agents may output signals every 1–60 minutes—pick one cadence per strategy.
– Key points: Set trading limits: max position size $1,000 and max daily loss $200 as defaults.
– Key points: Integrate with a kill-switch for 1-click emergency stop.
– Key points: Allocate 30 requests/min per account as a safe API usage baseline.
Watch out for: overfitting and black-box decisions; require documented overrides and human review every 24 hours.
5. DIY bots and Selenium scraping — 2 pip installs and 1 run command (quick POC)
DIY automation uses a scripted browser to control the eToro web UI. This approach is fastest for proofs-of-concept. It is fragile and has compliance risk if it violates platform terms.
Quick install and run commands:
– Install two Python packages: pip install selenium and pip install pandas.
– Typical run command: python3 main.py.
– Example community repo stats: one simple bot repo shows 30 stars, 10 forks, and 3 watchers.
Build steps and numbers:
– Scrape signals from public sources such as Yahoo Finance or other free feeds. Pull data every 1–60 minutes depending on strategy.
– Map signals to trade logic. Define position sizing rules: e.g., use $50–$500 per trade or 1%–2% of account equity.
– Automate order placement through the eToro web UI via Selenium. Use XPath or CSS selectors; maintain 10–20 selectors for the core flows.
Performance and maintenance estimates:
– Expect 1–3 maintenance breaks per month due to UI changes. Schedule a regression test every 7 days.
– For simple bots, plan 2–4 hours of maintenance per break. For complex bots, plan 4–12 hours.
– Test on demo: run the bot for 14 days or at least 30 demo trades before any live use.
Legal and reliability limits:
– This approach often bypasses official APIs and can trip automated login protections. Expect CAPTCHAs and 2FA prompts.
– eToro terms may restrict scripted UI interactions; get written approval for multi-user or company deployments.
Best for: Fast proof-of-concept and scraping-only automation.
Skip if: You need reliable, supported execution for live trading or must comply strictly with platform terms.
Key points:
– Key points: Install 2 pip packages and run python3 main.py to start the POC.
– Key points: Use data cadences of 1–60 minutes for signals.
– Key points: Expect 1–3 UI breaks per month; run regressions every 7 days.
– Key points: Map position sizing to $50–$500 or 1%–2% of equity per trade.
– Key points: Example repo shows 30 stars, 10 forks, 3 watchers as community indicators.
Watch out for: automated login protections, CAPTCHAs, and account blocks; always use demo first.
6. Risk management, compliance, and testing — 2 regulatory IDs and simple rules
Understand the regulatory context. eToro entities operate under licensed permissions. Two identifiers you should know: ADGM FSRA permission number 220073 and the NMLS ID for the U.S. entity 1769299. Confirm which entity holds your account and follow their local rules.
Concrete risk rules to apply:
– Position sizing: limit any single trade to ≤2% of account equity. For a $10,000 account, that equals $200 per trade.
– Daily loss limit: set a hard stop at 5% of capital. For $50,000 equity, stop trading if losses exceed $2,500 in a day.
– Backtest requirement: validate strategies on at least 100 trades or 30 calendar days before live rollout. Prefer 200 trades or 90 days for volatile strategies.
Compliance and audit steps:
– Log all orders and API calls for 90 days. Store logs at 1-minute resolution during critical hours.
– Retain trade and P&L snapshots every 1 minute during market hours for strategies with intraday exposure.
– Keep trade confirmations and account statements for at least 3 tax reporting cycles if required by your local jurisdiction.
Insurance and protection numbers:
– Enable account protection: use 2FA with SMS plus an authenticator app. Require 2FA for all key rotations and new key creation.
– Keep a cash buffer of 5%–10% of capital for margin or volatility. For a $20,000 account, keep $1,000–$2,000 reserved.
Operational checklists:
– Set kill-switch thresholds: 1-click stop if daily loss > 5% or if any single trade loses > 3% of capital.
– Require written consent for programmatic access on multi-user or managed accounts.
– Review agent decisions every 24 hours and perform manual audits every 7 days.
Best for: Maintaining compliant, auditable automated trading with firm-level controls.
Skip if: You will not keep persistent logs or cannot enforce 2FA and key rotation.
Key points:
– Key points: Apply position sizing ≤2% per trade; for $10,000 equity, this is $200.
– Key points: Set a hard daily stop at 5% of capital; for $50,000 equity, stop at $2,500.
– Key points: Backtest on 100 trades or 30 days minimum; prefer 200 trades or 90 days.
– Key points: Log API calls and orders for 90 days; keep 1-minute snapshots during market hours.
– Key points: Keep a cash buffer of 5%–10% of capital for margin needs.
Watch out for: programmatic execution without written consent in multi-user setups.
Comparison table — options at a glance (intro + table + summary)
Use this table to compare setup effort, trading capability, and limits across the four primary options. Pick a row that matches your skills and capital.
| Method | Setup Difficulty (1–5) | Live Trading | Best for | Key limits / costs |
|---|---|---|---|---|
| Official eToro API | 3 | Yes | Developers; full control | Request cap 60/min recommended; rotate keys every 90 days; demo $100,000 |
| CopyTrader / Smart Portfolios | 1 | Yes | Passive investors; no code | 0 extra copying fee; allocation 10%–30%; demo $100,000 |
| Tori / Agentic platforms | 2 | Yes | AI signal orchestration | Test 100–200 demo trades; set max pos $1,000; 30 req/min baseline |
| DIY Selenium bots | 4 | Yes (fragile) | Quick POC; scraping | 2 pip installs; run python3 main.py; expect 1–3 breaks/month |
Summary:
– Official API provides the most control and auditability. Expect a medium setup cost rated 3/5.
– CopyTrader and Smart Portfolios are the simplest at 1/5 and cost you no copying fees. Use for passive allocations of 10%–30%.
– Agentic platforms give AI orchestration at moderate difficulty. Run 100–200 demo trades before live.
– Selenium bots are fastest for POCs but fragile. Plan for 1–3 monthly maintenance events.
Closing — Decision tree and next steps
Decide in 5 steps:
1) Skill check: If you can write and secure server code, choose the Official API. Expect 2 key types and 3 auth flows. Test 100 demo trades.
2) Time and oversight: If you want no-code, use CopyTrader/Smart Portfolios. Allocate 10%–30% of capital per strategy.
3) AI signals: If you want agentic orchestration, pick Tori or agent platforms. Integrate keys in 10–30 minutes and test 100–200 demo trades for 7–14 days.
4) Fast POC: If you need a quick prototype, use Selenium. Install 2 pip packages and run python3 main.py. Limit exposure and use demo for 14 days.
5) Risk gates: Always set position sizing ≤2% per trade and a daily stop at 5% of capital. Keep a 5%–10% cash buffer.
Next steps checklist:
– Request eToro API access and enable demo $100,000 for testing.
– Choose one path and assign 1 responsible person to run daily checks.
– Implement logging: record every action and keep logs for 90 days.
– Run the chosen approach in demo for at least 30 days or 100 trades.
– Move to live only after passing the 30-day or 100-trade gate and confirming your kill-switch works in under 1 minute.
Follow these steps. Test thoroughly. Limit exposure. Log everything. Start small and scale with clear rules.