Skip to main content
POST
/
api
/
v1
/
posts
/
{postId}
/
comments
/
{commentId}
/
replies
/
{replyId}
/
likes
Like a reply
curl --request POST \
  --url https://public-api.etoro.com/api/v1/posts/{postId}/comments/{commentId}/replies/{replyId}/likes \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-request-id: <x-request-id>' \
  --header 'x-user-key: <x-user-key>' \
  --data '{}'

Authorizations

​
Authorization
string
header
required

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

​
x-request-id
string<uuid>
required

A unique request identifier.

Example:

"a4cdc93e-4a46-4b7a-99a1-fc4e2a35fb63"

​
x-api-key
string<password>
required

API key for authentication.

Example:

"lhgfaslk21490FAScVPkdsb53F9dNkfHG4faZSG5vfjndfcfgdssdgsdHF4663"

​
x-user-key
string<password>
required

User-specific authentication key.

Example:

"eyJlYW4iOiJVbnJlZ2lzdGVyZWRBcHBsaWNhdGlvbiIsImVrIjoiOE5sZ2cwcW5EUVdROUFNWGpXT2lmOWktZnpidG5KcUlqWGJ3WHJZZkpZcldrbG90ZEhvLVBjSWhQaU8xU1ZtMW84aU1WZGZqN2xWNzFjLXFxLmcybXE1dnh4Q1hUT25xaWRUaTFlcEhmVk1fIn0_"

Path Parameters

​
postId
string<uuid>
required

ID of the parent post (UUID)

​
commentId
string<uuid>
required

ID of the parent comment (UUID)

​
replyId
string<uuid>
required

ID of the reply (UUID)

Body

application/json

Empty JSON object. The body must be present but contains no fields.

Response

Like recorded successfully