eToro API GET /api/v1/trading/info/demo/close-orders/{orderId}
Looks up one close order on the demo account: its status and the positions it closed. This is the call that confirms a close.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
Read on eToro's own reference page on 12 Oct 2026: method, path, parameters and the top level response fields. A Read key is enough (OAuth scopes etoro-public:demo:read or etoro-public:trade.demo:read, or their write forms). The identifier values in the mock are placeholders: the meanings of statusID, orderType and operationType were not read. Documented rate limit: 60 requests per 60 seconds, shared with related endpoints.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| x-request-idrequired | header | string | A fresh UUID for every request. |
| orderIdrequired | path | integer | ID of the close order. |
Authentication headers
| Name | Type | Description |
|---|---|---|
| x-api-keyrequired | string | Your public API key, which identifies the application. Sent with x-user-key; eToro's reference says an OAuth 2.0 bearer token can be used instead of the key pair, not alongside it. Placeholder only: never paste a real key into this site. |
| x-user-keyrequired | string | Your user key from Settings > Trading > API Key Management. Each key is tied to one environment (Demo or Real) and to Read or Write permission. Placeholder only. |
Request
Written from the method, path and parameters recorded on this page. No demo host is recorded as a plain address for this API, so the samples read the base address from an environment variable. Not executed against a live or demo account. Credentials are read from environment variables on your own machine and are never entered on this site. The request builder writes these same snippets, from the same record.
Python
# Set ETORO_BASE_URL, ETORO_API_KEY, ETORO_USER_KEY as environment variables first. Never paste real values into code.
# No demo host is recorded as a plain address for this API, so the base address is read from ETORO_BASE_URL.
# Replace each {placeholder}, "..." and 0 with a real value before running.
import os
import requests
BASE_URL = os.environ["ETORO_BASE_URL"]
headers = {
"x-api-key": os.environ["ETORO_API_KEY"],
"x-user-key": os.environ["ETORO_USER_KEY"],
"x-request-id": "...",
}
resp = requests.get(BASE_URL + "/api/v1/trading/info/demo/close-orders/{orderId}", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())JavaScript
// Set ETORO_BASE_URL, ETORO_API_KEY, ETORO_USER_KEY as environment variables first. Never paste real values into code.
// No demo host is recorded as a plain address for this API, so the base address is read from ETORO_BASE_URL.
// Replace each {placeholder}, "..." and 0 with a real value before running.
// Run as a module, for example a .mjs file, on a Node version that has fetch built in.
const BASE_URL = process.env.ETORO_BASE_URL;
const res = await fetch(BASE_URL + "/api/v1/trading/info/demo/close-orders/{orderId}", {
method: "GET",
headers: {
"x-api-key": process.env.ETORO_API_KEY,
"x-user-key": process.env.ETORO_USER_KEY,
"x-request-id": "...",
},
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());curl
# Set ETORO_BASE_URL, ETORO_API_KEY, ETORO_USER_KEY as environment variables first. Never paste real values into code.
# No demo host is recorded as a plain address for this API, so the base address is read from ETORO_BASE_URL.
# Replace each {placeholder}, "..." and 0 with a real value before running.
curl -X GET "$ETORO_BASE_URL/api/v1/trading/info/demo/close-orders/{orderId}" \
-H "x-api-key: $ETORO_API_KEY" \
-H "x-user-key: $ETORO_USER_KEY" \
-H "x-request-id: ..."Response
A mock response. The values are invented, so check field names against the official reference.
{
"_mock": true,
"orderID": 900003,
"CID": 1000001,
"statusID": 1,
"orderType": 1,
"operationType": 1,
"instrumentID": 999001,
"assetCurrencyID": 1,
"accountCurrencyID": 1,
"requestOccurred": "2026-09-18T08:10:00Z",
"proceeds": 101.2,
"externalOperationType": 0,
"positions": []
}Limits that apply at eToro
| Limit | Value | Scope | Source |
|---|---|---|---|
| Headline limit | 60/min reads per key | user | api-portal.etoro.comchecked |
eToro API errors you may meet
- ApiKeyRequiredThe Authenticate message was sent without the API key. eToro lists this among the error codes of an unsuccessful WebSocket Authenticate response.
- HTTP 400HTTP 400. Validation failed on the request as sent, for example a missing or malformed minDate or too many instrument IDs in one call.
- DataRequiredThe Authenticate message was sent without its data. eToro lists this among the error codes of an unsuccessful WebSocket Authenticate response.
- HTTP 403HTTP 403. The key or token is recognised but lacks the permission this call needs.
- InvalidKeyA key in the Authenticate message is not valid. eToro lists this among the error codes of an unsuccessful WebSocket Authenticate response.
- HTTP 404HTTP 404. The order, position or username in the request was not found. eToro also uses 404 for some upstream or validation failures.
All eToro API error codes, including 10 more not listed here.