Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Security Deck
  • Pricing policy
    • Authentication
      • Overview
        • Overview
        • List
        • Create
  • Audit Trails events
  • Release notes

In this article:

  • HTTP request
  • Path parameters
  • Query parameters
  • Response
  • Comment
  • Actor
  • Subject
  • Sensor
  1. API reference
  2. REST (англ.)
  3. Comment
  4. List

Security Deck Alerts API, REST: Comment.List

Written by
Yandex Cloud
Updated at February 3, 2026
  • HTTP request
  • Path parameters
  • Query parameters
  • Response
  • Comment
  • Actor
  • Subject
  • Sensor

List comments.

HTTP requestHTTP request

GET https://alert-sink.api.cloud.yandex.net/securitydeck/alerts/v1/alerts/{alertId}/comments

Path parametersPath parameters

Field

Description

alertId

string

Required field. Alert ID.

The maximum string length in characters is 50.

Query parametersQuery parameters

Field

Description

pageSize

string (int64)

Number of results per page.

The maximum value is 1000.

pageToken

string

Token for the results page.

The maximum string length in characters is 200.

ResponseResponse

HTTP Code: 200 - OK

{
  "comments": [
    {
      "id": "string",
      "alertId": "string",
      "createdBy": {
        // Includes only one of the fields `subject`, `sensor`
        "subject": {
          "id": "string"
        },
        "sensor": {
          "id": "string"
        }
        // end of the list of possible fields
      },
      "createTime": "string",
      "updatedBy": {
        // Includes only one of the fields `subject`, `sensor`
        "subject": {
          "id": "string"
        },
        "sensor": {
          "id": "string"
        }
        // end of the list of possible fields
      },
      "updateTime": "string",
      "text": "string"
    }
  ],
  "nextPageToken": "string"
}

Field

Description

comments[]

Comment

Requested comments.

nextPageToken

string

Token for the next results page.

CommentComment

A comment.

Field

Description

id

string

Comment ID.

alertId

string

ID of the alert the comment is for.

createdBy

Actor

Who created the comment.

createTime

string (date-time)

Comment creation date.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

updatedBy

Actor

Who modified the comment last.
Optional. Not present if comment was not modified after initial creation.

updateTime

string (date-time)

When was the comment last modified.
Optional. Not present if comment was not modified after initial creation.

String in RFC3339 text format. The range of possible values is from
0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the
Protocol Buffers reference.
In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

text

string

The comment contents. Yandex Flavored Markdown.

ActorActor

Information about an entity that performed an action (created an alert, added a comment, etc.).

Field

Description

subject

Subject

Action was performed by a specific Cloud subject.

Includes only one of the fields subject, sensor.

sensor

Sensor

Action was performed by (or on behalf of) an alert provider system (aka sensor)

Includes only one of the fields subject, sensor.

SubjectSubject

Cloud subject.

Field

Description

id

string

Subject ID.

SensorSensor

Alert provider system (aka sensor).

Field

Description

id

string

Sensor ID.

Was the article helpful?

Previous
Overview
Next
Create
© 2026 Direct Cursus Technology L.L.C.