Skip to main content
GET
/
api
/
v1
/
notifications
/
messages
Get in-app notifications
curl --request GET \
  --url https://public-api.etoro.com/api/v1/notifications/messages \
  --header 'Authorization: Bearer <token>' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-request-id: <x-request-id>' \
  --header 'x-user-key: <x-user-key>'
{
  "messages": [
    {
      "messageId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "correlationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "actionLink": "<string>",
      "imageTitle": "<string>",
      "imageUrl": "<string>",
      "notificationType": "<string>",
      "version": "<string>",
      "aggregatable": true,
      "grouped": true,
      "aggregationId": "<string>",
      "message": "<string>",
      "publishDate": "2023-11-07T05:31:56Z",
      "subCategory": "<string>",
      "category": "<string>",
      "rtlLanguage": true,
      "section": "<string>"
    }
  ],
  "meta": {
    "notSeen": 5
  }
}

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:

"2f8404d8-497e-4b2c-ae9b-fee541eecf30"

x-api-key
string<password>
required

API key for authentication.

Example:

"lhgfaslk21490FAScVPkdsb53F9dNkfHG4faZSG5vfjndfcfgdssdgsdHF4663"

x-user-key
string<password>
required

User-specific authentication key.

Example:

"eyJlYW4iOiJVbnJlZ2lzdGVyZWRBcHBsaWNhdGlvbiIsImVrIjoiOE5sZ2cwcW5EUVdROUFNWGpXT2lmOWktZnpidG5KcUlqWGJ3WHJZZkpZcldrbG90ZEhvLVBjSWhQaU8xU1ZtMW84aU1WZGZqN2xWNzFjLXFxLmcybXE1dnh4Q1hUT25xaWRUaTFlcEhmVk1fIn0_"

Response

Notifications retrieved successfully

Response containing notifications and metadata

messages
object[]

List of notification messages

meta
object

Metadata about the notifications result