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

The eToro API supports two authentication methods. Both use the same base URL and endpoints — only the auth headers differ.

Method 1 — OAuth SSO (Bearer Token)

If the user authenticated via "Login with eToro" (SSO/OAuth), an access_token is available from the token exchange.

Headers (every request):

• - x-request-id: unique UUID per request
• INLINECODE3: INLINECODE4

Where access_token comes from:

1. 1. User clicks "Login with eToro" → redirects to https://www.etoro.com/sso/ with PKCE challenge.
2. User authenticates on eToro's side.
3. eToro redirects back with an authorization code.
4. The code is exchanged for tokens via POST https://www.etoro.com/sso/oidc/token:

- grant_type=authorization_code - code=<auth_code> - redirect_uri=<callback_url> - code_verifier=<pkce_verifier> - Plus Authorization: Basic <base64(client_id:client_secret)> header

1. 5. Response contains:

- access_token — this is the Bearer token for API calls (~2130 chars, JWT) - id_token — JWT with user identity (sub claim = 128-char encoded user ID) - token_type: "Bearer" - expires_in: (varies)

Example:

CODEBLOCK0

Method 2 — Manual API Keys

If the user provides API keys manually (no OAuth), use key-based auth.

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
• INLINECODE21: Public API Key (<PUBLIC_KEY>)
• INLINECODE23: User Key (<USER_KEY>)

Example:

CODEBLOCK1

Choosing the Auth Method in Code

When making requests, check which credentials are available:

CODEBLOCK2

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.

CODEBLOCK3

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

CODEBLOCK4

Note: The examples above use OAuth (Bearer token). For API key auth, replace the Authorization header with x-api-key and x-user-key headers instead.

Common IDs

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

Market Data (Requests)

Search instruments

• - INLINECODE67
• Required query: fields (comma-separated list of instrument fields to return)
• Optional: searchText, pageSize, pageNumber, INLINECODE72
• 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

• - INLINECODE80

Filters: instrumentIds, exchangeIds, stocksIndustryIds, instrumentTypeIds.

Prices & history

• - INLINECODE85

Required: instrumentIds (comma-separated).

• - INLINECODE87

Returns historical closing prices for all instruments (bulk).

• - INLINECODE88

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)
• INLINECODE96
• INLINECODE97 (optional stocksIndustryIds)

Trading Execution (Requests)

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

Market Open Orders (by amount)

Endpoints:

• - INLINECODE99
• INLINECODE100

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, INLINECODE104
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE109

Market Open Orders (by units)

Endpoints:

• - INLINECODE110
• INLINECODE111

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, INLINECODE115
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE120

Cancel Market Open Orders

Endpoints:

• - INLINECODE121
• INLINECODE122

Market Close Orders

Endpoints:

• - INLINECODE123
• INLINECODE124
• INLINECODE125
• INLINECODE126

Body (JSON):

• - Required: INLINECODE127
• 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:

• - INLINECODE134
• INLINECODE135
• INLINECODE136
• INLINECODE137

Body (PascalCase, JSON):

• - Required: InstrumentID, IsBuy, Leverage, Rate, and one of Amount or INLINECODE143
• Optional: StopLossRate, TakeProfitRate, IsTslEnabled, IsNoStopLoss, INLINECODE148
• Do not send: IsDiscounted, INLINECODE150

Trading Info & Portfolio (Requests)

• - INLINECODE151
• INLINECODE152
• INLINECODE153
• INLINECODE154

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

• - INLINECODE157

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

Watchlists (Requests)

User watchlists

• - INLINECODE161

Optional: itemsPerPageForSingle, ensureBuiltinWatchlists, addRelatedAssets.

• - INLINECODE165

Optional: pageNumber, itemsPerPage.

• - INLINECODE168

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

• - INLINECODE172

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

• - INLINECODE174

Watchlist items (body schema)

INLINECODE175 fields:

• - ItemId (required, int)
• INLINECODE177 (required, string: Instrument or Person)
• INLINECODE180 (optional, int)

Endpoints:

• - INLINECODE181
• INLINECODE182
• INLINECODE183

Example body:

CODEBLOCK5

Default watchlists

• - INLINECODE184
• INLINECODE185

Optional: itemsLimit, itemsPerPage.

• - INLINECODE188

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

• - INLINECODE192
• INLINECODE193

Query: newRank (required).

Public watchlists

• - INLINECODE195
• INLINECODE196

Feeds (Requests)

Read feeds

• - INLINECODE197

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

• - INLINECODE203

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).
• INLINECODE211 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

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

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

Minimal example:

CODEBLOCK6

Curated Lists & Recommendations (Requests)

• - INLINECODE226
• INLINECODE227

Popular Investors (Copiers)

• - INLINECODE228

User Info & Analytics (Requests)

• - INLINECODE229

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

• - INLINECODE233

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

• - INLINECODE250
• INLINECODE251

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

• - INLINECODE257
• INLINECODE258

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

Responses & Schemas

For response schemas and full examples, refer to:

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