eToro Public API

Base URL: INLINECODE0

About

This skill allows to interact with the user's eToro account programatically, including executing trades.

Authentication & Required Headers

Keys (request from the user on install)

• - Public API Key: application
• User Key: user account
• Environment: Real Portfolio or Virtual Portfolio (real/demo)

Key generation (user-facing):

1. 1. Log in to eToro.
2. Settings > Trading.
3. Create New Key.
4. Choose Environment (Real or Virtual/Demo) and Permissions (Read or Write).
5. Verify identity and copy the generated User Key.

Headers (every request):

• - x-request-id: unique UUID per request
• INLINECODE2: Public API Key (KEY>)
• INLINECODE3: User Key (KEY>)

Example:

CODEBLOCK0

Request Conventions

• - All paths below are relative to the Base URL (which already includes /api/v1).

Example: GET /watchlists means GET https://public-api.etoro.com/api/v1/watchlists.

• - Query params go in the URL, path params go in the URL path.
• For query params that are documented as array, send them as comma-separated values (e.g., instrumentIds=1001,1002).
• Pagination patterns vary by endpoint:

- Search: pageNumber, pageSize - People search & trade history: page, pageSize - Feeds: take, offset - Watchlist items listing: pageNumber, itemsPerPage

• - Casing matters for request bodies:

- Trading execution uses PascalCase fields (e.g., InstrumentID, IsBuy, Leverage). - Market close body uses InstrumentId (capital I, lowercase d). - Watchlist items use ItemId, ItemType, ItemRank. - Feeds post body uses lower camel (owner, message, tags, mentions, attachments).

• - Some responses may use different casing for similar concepts (e.g., instrumentId vs InstrumentID). When extracting IDs, handle both if present.

Demo vs Real Trading

• - Use demo execution endpoints (contain /demo/) for testing and paper trading.
• Use non-demo execution endpoints for real trading.
• For portfolio/PnL:

- Demo: /trading/info/demo/* - Real: /trading/info/portfolio and /trading/info/real/pnl

• - Ensure your key environment matches the endpoint (Virtual vs Real). Each User Key is associated with a specific environment.

Use Defaults

• - Important: You don't need to specify all parameters. If the user doesn't specify leverage for example, don't send it on the API request.

Quick Start (Demo Trade)

1. 1. Resolve instrumentId using search.

fields is required on search requests.

CODEBLOCK1

1. 2. Place a demo market order by amount (PascalCase body):

CODEBLOCK2

Common IDs

• - instrumentId: from Search or Instruments metadata
• INLINECODE38: from Portfolio endpoints
• INLINECODE39: from execution responses or Portfolio endpoints
• INLINECODE40: used by instrument feed endpoints (typically available in instrument metadata/search fields)
• INLINECODE41: numeric eToro user ID (often referred to as CID in responses; discover via People endpoints/search)
• INLINECODE42: from watchlists list/create endpoints

Market Data (Requests)

Search instruments

• - INLINECODE43
• Required query: fields (comma-separated list of instrument fields to return)
• Optional: searchText, pageSize, pageNumber, INLINECODE48
• The Search endpoint supports filtering by fields returned in results; for exact symbol lookup, use internalSymbolFull as a query param and verify the exact match.
• Recommended minimal fields when you need IDs: include the instrument identifier (may appear as instrumentId or InstrumentID), plus internalSymbolFull and displayname (and marketId if you plan to use Feeds).

Metadata

• - INLINECODE56

Filters: instrumentIds, exchangeIds, stocksIndustryIds, instrumentTypeIds.

Prices & history

• - INLINECODE61

Required: instrumentIds (comma-separated).

• - INLINECODE63

Returns historical closing prices for all instruments (bulk).

• - INLINECODE64

direction: asc or desc. candlesCount max 1000. Use only supported interval values (confirm via docs if unsure).

Reference data

• - GET /market-data/exchanges (optional exchangeIds)
• INLINECODE72
• INLINECODE73 (optional stocksIndustryIds)

Trading Execution (Requests)

Requires a key with appropriate permissions (typically Write) and the correct environment (Demo vs Real).

Market Open Orders (by amount)

Endpoints:

• - INLINECODE75
• INLINECODE76

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, INLINECODE80
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE85

Market Open Orders (by units)

Endpoints:

• - INLINECODE86
• INLINECODE87

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, INLINECODE91
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE96

Cancel Market Open Orders

Endpoints:

• - INLINECODE97
• INLINECODE98

Market Close Orders

Endpoints:

• - INLINECODE99
• INLINECODE100
• INLINECODE101
• INLINECODE102

Body (JSON):

• - Required: INLINECODE103
• Optional: UnitsToDeduct (number or null)

Partial close: set UnitsToDeduct.
Full close: set UnitsToDeduct to null.
You must close by positionId, not by symbol.

Market-if-touched (Limit) Orders

Endpoints:

• - INLINECODE110
• INLINECODE111
• INLINECODE112
• INLINECODE113

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, Rate, and one of Amount or INLINECODE119
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE124
• Do not send: IsDiscounted, INLINECODE126

Trading Info & Portfolio (Requests)

• - INLINECODE127
• INLINECODE128
• INLINECODE129
• INLINECODE130

Use these to discover positionId and orderId for close/cancel flows.

• - INLINECODE133

Required: minDate (YYYY-MM-DD). Optional: page, pageSize.

Watchlists (Requests)

User watchlists

• - INLINECODE137

Optional: itemsPerPageForSingle, ensureBuiltinWatchlists, addRelatedAssets.

• - INLINECODE141

Optional: pageNumber, itemsPerPage.

• - INLINECODE144

Query: name (required), type, dynamicQuery (optional). (Uses query params, not a JSON body.)

• - INLINECODE148

Query: newName (required). (Uses query params, not a JSON body.)

• - INLINECODE150

Watchlist items (body schema)

INLINECODE151 fields:

• - ItemId (required, int)
• INLINECODE153 (required, string: Instrument or Person)
• INLINECODE156 (optional, int)

Endpoints:

• - INLINECODE157
• INLINECODE158
• INLINECODE159

Example body:

CODEBLOCK3

Default watchlists

• - INLINECODE160
• INLINECODE161

Optional: itemsLimit, itemsPerPage.

• - INLINECODE164

Query: name (required), type, dynamicQuery (optional).

• - INLINECODE168
• INLINECODE169

Query: newRank (required).

Public watchlists

• - INLINECODE171
• INLINECODE172

Feeds (Requests)

Read feeds

• - INLINECODE173

Optional: requesterUserId, take, offset, badgesExperimentIsEnabled, reactionsPageSize.

• - INLINECODE179

Optional: requesterUserId, take, offset, badgesExperimentIsEnabled, reactionsPageSize.

Notes:

• - marketId is associated with an instrument (typically available via instrument metadata/search if you include it in fields).
• INLINECODE187 is a numeric user identifier (CID). If you only have a username, discover the numeric ID via People endpoints (see User Info & Analytics).

Create post

• - INLINECODE188
• Body fields (lower camel, JSON):

- owner (int) - message (string) - tags: { "tags": [{ "name": "...", "id": "..." }] } - mentions: { "mentions": [{ "userName": "...", "id": "...", "isDirect": true }] } - attachments: array of objects with url, title, host, description, mediaType, and optional media.

Minimal example:

CODEBLOCK4

Curated Lists & Recommendations (Requests)

• - INLINECODE202
• INLINECODE203

Popular Investors (Copiers)

• - INLINECODE204

User Info & Analytics (Requests)

• - INLINECODE205

Optional: usernames, cidList. Use this to map username ↔ CID (userId) when you need numeric userId for feeds/public watchlists.

• - INLINECODE209

Required: period. Optional: page, pageSize, sort, popularInvestor, gainMax, maxDailyRiskScoreMin, maxDailyRiskScoreMax, maxMonthlyRiskScoreMin, maxMonthlyRiskScoreMax, weeksSinceRegistrationMin, countryId, instrumentId, instrumentPctMin, instrumentPctMax, isTestAccount, and other filters.

• - INLINECODE226
• INLINECODE227

Required: minDate, maxDate, type (Daily or Period).

• - INLINECODE233
• INLINECODE234

Required: period (e.g., LastTwoYears).

Responses & Schemas

For response schemas and full examples, refer to:

• - https://api-portal.etoro.com/
• MCP server: INLINECODE237