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
        • Get
        • Update
  • Audit Trails events
  • Release notes

In this article:

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

Security Deck Alerts API, REST: Alert.Get

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

Get alert by ID.

HTTP requestHTTP request

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

Path parametersPath parameters

Field

Description

alertId

string

Required field. Alert ID.

Query parametersQuery parameters

Field

Description

languageCode

string

Language code. What language should alert texts be in.
Supported values: "en_US" for English, "ru_RU" for Russian.
If requested language is unavailable, language-dependent fields will be omitted.
Optional. Defaults to "en_US" if not specified.

The maximum string length in characters is 10.

detailsI18n

boolean

Should alert details be internationalized (true) or left in source representation (false).

ResponseResponse

HTTP Code: 200 - OK

{
  "id": "string",
  "sinkId": "string",
  "title": "string",
  "description": "string",
  "recommendations": "string",
  "severity": "string",
  "status": "string",
  "category": {
    "name": "string"
  },
  "classification": "string",
  "createdBy": {
    // Includes only one of the fields `subject`, `sensor`
    "subject": {
      "id": "string"
    },
    "sensor": {
      "id": "string"
    }
    // end of the list of possible fields
  },
  "assignee": {
    // Includes only one of the fields `subject`
    "subject": {
      "id": "string"
    }
    // end of the list of possible fields
  },
  "createTime": "string",
  "updateTime": "string",
  "details": "object"
}

Security Deck alert.

Field

Description

id

string

ID of the alert.

sinkId

string

ID of the alert sink alert is in.

title

string

Alert title. Plain text in requested language.

description

string

Alert description. Yandex Flavored Markdown in requested language.
Optional. Only present in Get method response.
May be absent in Get method response if description is not available in requested language.

recommendations

string

Alert recommendations. Yandex Flavored Markdown in requested language.
Optional. Only present in Get method response.
May be absent in Get method response if recommendations are not available in requested language.

severity

enum (Severity)

Alert severity.

  • INFO: Informational severity
  • LOW: Low severity
  • MEDIUM: Medium severity
  • HIGH: High severity

status

enum (Status)

Alert status.

  • OPEN: Status is "open". Alert is not being currently processed.
  • IN_PROGRESS: Status is "in progress". Alert assignee is currently processing the alert.
  • NEED_INFO: Status is "need info". Alert assignee cannot currently process the alert and requires additional information.
  • RESOLVED: Status is "resolved". Alert processing has concluded.

category

Category

Alert category (aka threat type).

classification

enum (Classification)

Alert classification.
Optional. Can be assigned after creation.

  • TRUE_POSITIVE: Alert represents an actual problem that needs to be mitigated.
  • BENIGN_POSITIVE: Alert represents a legitimate problem but does not require attention.
  • FALSE_POSITIVE: Alert represents something that's not an issue.
  • UNDETERMINED: Alert relevance cannot be determined.

createdBy

Actor

Who created the alert.

assignee

Assignee

Who the alert is assigned to.
Optional. Can be assigned after creation.

createTime

string (date-time)

Alert creation time.
This time is reported by alert creator and can generally be different from the moment the alert record was created.
E.g. a security event occurred at time A and it took B amount of time to deliver the alert to the Alert Sink.
This time is the A and not the A+B.

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).

updateTime

string (date-time)

Alert modification time.
Represents last time alert record itself was modified, not including anything alert-related (comments, etc.)
Equals to create_time immediately after 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).

details

object

Alert technical details.
Optional. Only present in Get method response.

CategoryCategory

Alert category.

Field

Description

name

string

Alert category name.

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.

AssigneeAssignee

Information about an entity that alert was assigned to.

Field

Description

subject

Subject

Alert is assigned to as specific Cloud subject.

Includes only one of the fields subject.

SubjectSubject

Cloud subject.

Field

Description

id

string

Subject ID.

Was the article helpful?

Previous
List
Next
Update
© 2026 Direct Cursus Technology L.L.C.