{
"id": "ed72693c-1545-4fa1-8a10-aca7cf5419a6",
"operation": "Subscribe",
"data": {
"topics": [
"instrument:100000"
],
"snapshot": false
}
}Subscribe (control channel)
All client requests share one JSON envelope: { "id": "<guid>", "operation": "<Authenticate|Subscribe|Unsubscribe>", "data": { ... } }. The server answers each request on the same connection with an acknowledgement that echoes the id and the operation. The id is a client-generated GUID used to correlate the request with its acknowledgement.
{
"id": "ed72693c-1545-4fa1-8a10-aca7cf5419a6",
"operation": "Subscribe",
"data": {
"topics": [
"instrument:100000"
],
"snapshot": false
}
}etoro API credentials, sent as a pair inside the Authenticate request's data object -- userKey (the user identifier) and apiKey (the secret) -- not as an HTTP header. Required before subscribing to the private topic; public market topics (instrument:<instrumentId>) need no authentication. Both values come from the API key section of etoro account settings, which appears once the account is verified.
GET
Subscribe to one or more topics.