eToro · Schema
InAppNotificationMessage
A single in-app notification message
Social TradingCopy TradingInvestingMarket DataPortfolio-ManagementFintechTradingStocksCryptocurrencyETFs
Properties
| Name | Type | Description |
|---|---|---|
| messageId | string | Unique identifier of the notification message |
| correlationId | string | Correlation ID for request tracing |
| actionLink | string | URL for the notification action |
| imageTitle | string | Title for the notification image |
| imageUrl | string | URL of the notification image |
| notificationType | string | Type of notification |
| version | string | Version of the notification format |
| aggregatable | boolean | Whether this notification can be aggregated |
| grouped | boolean | Whether this notification is grouped |
| aggregationId | string | ID for aggregation grouping |
| message | string | Notification content text |
| readStatus | string | Current read status of the notification |
| publishDate | string | When the notification was published |
| subCategory | string | Sub-category of the notification |
| category | string | Category of the notification |
| rtlLanguage | boolean | Whether the notification content is in an RTL language |
| section | string | Section the notification belongs to |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/etoro/refs/heads/main/json-schema/InAppNotificationMessage.json",
"title": "InAppNotificationMessage",
"type": "object",
"description": "A single in-app notification message",
"properties": {
"messageId": {
"type": "string",
"format": "uuid",
"description": "Unique identifier of the notification message",
"example": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
},
"correlationId": {
"type": "string",
"format": "uuid",
"description": "Correlation ID for request tracing"
},
"actionLink": {
"type": "string",
"description": "URL for the notification action"
},
"imageTitle": {
"type": "string",
"description": "Title for the notification image"
},
"imageUrl": {
"type": "string",
"description": "URL of the notification image"
},
"notificationType": {
"type": "string",
"description": "Type of notification"
},
"version": {
"type": "string",
"description": "Version of the notification format"
},
"aggregatable": {
"type": "boolean",
"description": "Whether this notification can be aggregated"
},
"grouped": {
"type": "boolean",
"description": "Whether this notification is grouped"
},
"aggregationId": {
"type": "string",
"description": "ID for aggregation grouping"
},
"message": {
"type": "string",
"description": "Notification content text"
},
"readStatus": {
"type": "string",
"enum": [
"New",
"Seen",
"Read"
],
"description": "Current read status of the notification"
},
"publishDate": {
"type": "string",
"format": "date-time",
"description": "When the notification was published"
},
"subCategory": {
"type": "string",
"description": "Sub-category of the notification"
},
"category": {
"type": "string",
"description": "Category of the notification"
},
"rtlLanguage": {
"type": "boolean",
"description": "Whether the notification content is in an RTL language"
},
"section": {
"type": "string",
"description": "Section the notification belongs to"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/InAppNotificationMessage"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.