Update Sub-Account User Token
Updates an existing sub-account user token’s scopes, IP whitelist, or expiration. At least one field must be provided.
Authorizations
eToro OAuth2. Each operation lists the scopes that grant access as separate security requirements (OpenAPI OR semantics): the caller's token only needs ONE of them — you do NOT need all of them. The same scopes back the x-api-key/x-user-key credential pair.
Headers
A unique request identifier.
"09c67ad1-8ebd-4295-8970-193e008e6417"
API key for authentication.
"lhgfaslk21490FAScVPkdsb53F9dNkfHG4faZSG5vfjndfcfgdssdgsdHF4663"
User-specific authentication key.
"eyJlYW4iOiJVbnJlZ2lzdGVyZWRBcHBsaWNhdGlvbiIsImVrIjoiOE5sZ2cwcW5EUVdROUFNWGpXT2lmOWktZnpidG5KcUlqWGJ3WHJZZkpZcldrbG90ZEhvLVBjSWhQaU8xU1ZtMW84aU1WZGZqN2xWNzFjLXFxLmcybXE1dnh4Q1hUT25xaWRUaTFlcEhmVk1fIn0_"
The encrypted sub-account identifier. The backend validates that it decrypts to a sub-account owned by the caller's token gcid.
Path Parameters
The unique identifier of the user token to update.
Body
The replacement scope names. When provided, must be a subset of the scopes returned by GET /api/v1/sub-accounts/etoro-trading/user-tokens/scopes.
["etoro-public:trade.real:read"]The replacement IPv4 whitelist.
["192.168.1.1"]The replacement UTC expiration.
"2026-12-31T23:59:59Z"
Response
User token updated successfully