Skip to main content
GET
Get a single post by ID

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:

"508839a7-1f29-4489-868f-711dec21cfad"

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 post to retrieve (UUID)

Query Parameters

take
integer<int32>
default:10

Number of inline comments to include in the response

Required range: x >= 0
badgesExperimentIsEnabled
boolean
default:false

Flag indicating whether to include user badges in the response

Response

Post retrieved successfully

A single discussion entry in a feed — wraps a Post with its interaction data

id
string

Discussion wrapper ID (same as post ID)

Example:

"3fa85f64-5717-4562-b3fc-2c963f66afa6"

post
object

Post data embedded inside a Discussion feed item

commentsData
object

Inline comments preview

emotionsData
object

Aggregated emotions (likes) on an entity

requesterContext
object

Requester's relationship state with the post

summary
object

Post-level engagement counters

reason
any | null

Why this post appears in the feed (ForYou only). May be null or an object: { type: 'followed-user'|'instrument-trending', sourceId, owner }

Example: