Frequently Asked Questions

You need an eToro account, API credentials from the developer portal, and a way to send HTTPS requests. Follow Getting Started on this site, then open api-portal.etoro.com for keys, scopes, and the full documentation. The public REST base URL is https://public-api.etoro.com/api/v1/.

Create or sign in to your eToro account and use the API Portal to generate credentials. You will use the x-api-key and x-user-key headers on each request. See also Quick Reference for endpoint discovery.

Yes. Access to the eToro API is free for eligible users; there is no separate API subscription fee. Usage is still subject to eToro terms, fair use, and rate limits. Always refer to the official documentation for the latest policies.

The API is language-agnostic: any environment that can send HTTPS requests and set headers works. Official and community SDKs are listed under SDKs & Tools. Examples and patterns are covered in Learn and on api-portal.etoro.com.

Send x-api-key and x-user-key with every authenticated call. Use x-request-id with a unique value per request for tracing and support. Details are in the authentication section of the API documentation.

A 401 usually means missing or invalid credentials, expired tokens, or calling an endpoint without the required scopes. Verify both keys, clock skew, and that your portal app is approved for the product you are calling. Cross-check request format against API Reference and your key settings on api-portal.etoro.com.

Keys identify your application and user context. They are not embedded in URLs; pass them as headers. Rotate keys from the portal if they are compromised. Never commit secrets to source control; use environment variables. See Getting Started and the portal for setup.

Limits depend on product and endpoint class. The authoritative table lives in Rate limits on the API Portal. Design clients to backoff and retry rather than hard-coding a single global number.

Treat 429 as a signal to slow down: exponential backoff, respect any Retry-After header when present, and reduce concurrency. Read rate limit guidance and spread polling across time windows where possible.

Use https://api-portal.etoro.com/getting-started/rate-limits on the official docs site. For endpoint-specific behavior, also check API Reference.

Yes, when your account and app are enabled for live trading and you use the appropriate real-money flows. Always confirm environment and risk settings in the portal and docs before sending orders. Demo and real environments are separate; see the next question.

Demo uses simulated funds for testing strategies without real capital at risk. Real trading moves actual balances. Use demo for integration tests; switch only when you are ready and permitted. Product pages on this site (for example Trading API (Demo) and Trading API (Real)) summarize capabilities; api-portal.etoro.com has the operational detail.

Use the trading execution endpoints under the public API base https://public-api.etoro.com/api/v1/. For example, opening by notional amount is done through /trading/execution/market-open-orders/by-amount (full path: https://public-api.etoro.com/api/v1/trading/execution/market-open-orders/by-amount). Follow API Reference for parameters, idempotency, and validation rules.

For streaming quotes, use the WebSocket product (see WebSocket API on this site). For snapshot or polled REST data, use endpoints such as GET https://public-api.etoro.com/api/v1/market-data/rates. Compare options in API Reference and Market Data.

Available instruments and identifiers are exposed through the market data and instruments endpoints documented on api-portal.etoro.com. Use Quick Reference to search and filter endpoints from this portal.

Use the historical and candle endpoints listed under Market Data in API Reference (paths are under https://public-api.etoro.com/api/v1/). Respect rate limits when backfilling data.

Check the HTTP status and response body, confirm headers (x-api-key, x-user-key, x-request-id), and validate the URL matches https://public-api.etoro.com/api/v1/ plus the correct path. Compare with working examples in Examples and the exact schema in API Reference.

Start with documentation, Learn, and the Community Hub. For chat, see the Discord link in the site footer. This FAQ complements those resources.

Use community channels linked from Community for developer discussion. For documentation issues, note the page URL on api-portal.etoro.com when reporting. Include x-request-id values for API incidents so support can trace requests.