How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Acronis Alert Manager API

Operational alerting across the Acronis platform — fetch, categorise, register and unregister alert types, and dismiss alerts, so an integration can drive its own monitoring surface from Acronis events.

Acronis Alert Manager API is one of 21 APIs that Acronis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Acronis, Alerts, and Monitoring. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 17 operations across 12 paths, and defines 28 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against a single base URL, https://dev-cloud.acronis.com/api/alert_manager/v1.

17 operations 12 paths 28 schemas 3 DELETE11 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://{datacenter}.acronis.com/api/alert_manager/v1
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Acronis Alert Manager API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth_2_0) using the clientCredentials, password and authorizationCode flows, exposing 2 scopes.

  • oauth_2_0 — OAuth 2.0 security scheme definition for a user authorization.

Paths & Operations 17

Across 12 paths, the API surfaces 17 operations — 3 DELETE, 11 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Operations 17
POST
/alerts
Creates and activates an alert.
Create an alert body → 200400401403
GET
/alerts
Fetches all alerts by optional filtering parameters.
Fetch all alerts 20 params → 200401403
DELETE
/alerts
Dismisses the alerts by optional filtering parameters. Alerts will be dismissed even if they have the orphaned flag. Note that if no filter is provided all alerts within the tenant scope will be dism…
Dismiss the alerts by filter 16 params → 204401403
GET
/alerts/{id}
Fetches the information about the alert by ID.
Fetch an alert by ID 2 params → 200400401403404
DELETE
/alerts/{id}
Dismisses an alert by ID.
Dismiss an alert by ID 1 param → 204400401403404
GET
/categories
Fetches a list of enabled categories.
Fetch categories 1 param → 200401403
GET
/count
Fetches the alert counters that may be grouped by optional parameters.
Fetch alert counters 4 params → 200400401403
GET
/status
Returns the last of the most critical alerts grouped by selected scope.
Fetch alerts grouped by scope 2 params → 200400401403414
GET
/types
Fetches all registered alert types.
Fetch all alert types 3 params → 200401403
POST
/types
Registers a new alert type.
Register new alert type body → 204400401403
GET
/types/{id}
Fetch registered alert type by ID.
Fetch an alert type by ID 1 param → 200401403404
DELETE
/types/{id}
Unregisters the alert type. All alerts of this type will be disabled.
Unregister an alert type by ID 1 param → 204404
GET
/resource_status
Fetches the resources' statuses that contain the alerts with the highest severity found for the resources. Resource with ID that was not found in resourceId parameter of any active alert considered t…
Fetch resources containing the highest severity alerts 2 params → 200401403414
GET
/customer_alerts_count
Fetches count of alerts per customer. This API uses extended barrier mode by default. Response does not include customers with no alerts.
Fetch partner's customer alerts count 16 params → 200401403
GET
/customer_alerts
Fetches alerts of the specified customers. This API uses extended barrier mode by default.
Fetch alerts grouped per customer 17 params → 200401403
GET
/stats
Returns count of active alerts and last modification time.
Get count of active alerts and last modification time → 200401403
PATCH
/alerts/{id}/false_positive
Marks or unmarks alert as false positive.
Mark alert as false positive 1 param body → 204400401403404

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are AlertView (14 properties), Type (12 properties), TenantCountResult (7 properties), Report (6 properties). Each schema is shown below with its type and property counts.

Context
object
Deprecated. Value of unique key for alerts with current type. Parameters of object can be only strings. Variable structure of context is specified with custom…
uuid
string
AlertID
object
1 property 1 required
Error
object
Base error object
6 properties 2 required
paging
object
Paging format.
1 property 1 required
AlertView
object
View of alert in responses.
14 properties 9 required
Category
object
An information about the alert category or alert type category.
3 properties 1 required
Report
object
Count report.
6 properties 1 required
ScopeStatus
object
Status of the selected scope.
2 properties 2 required
OSType
string
Type
object
An information about the alert type.
12 properties 7 required
ResourceStatus
object
3 properties 2 required
CustomerAlertCount
object
4 properties 4 required
CustomerAlerts
object
2 properties 2 required
Statistics
object
2 properties 1 required
kbLinkInfo
object
Components for kblink
6 properties 6 required
debugInfo
object
Error debug information (map type)
cursors
object
Cursors before and after the current page.
2 properties
SeveritiesAndTypesEmbed
object
Alert counters grouped by severity and then by type.
4 properties 4 required
SeveritiesEmbed
object
Alert counters per severity.
4 properties 4 required
CategoriesEmbed
object
Alert counters per alert category. Object keys are identifiers of alert categories, values are counters of alerts of these categories.
TypesEmbed
object
Alert counters per alert type. Object keys are identifiers of alert types, values are counters of alerts of these types.
TenantCountResult
object
Alert counters for a tenant.
7 properties 3 required
Status
object
Status of any scope that represents the last alert with the highest severity in the scope.
5 properties 5 required
ACEPKeyValue
object
Key-value mapping between context fields and ACEP fields. It is mostly for internal use only.
3 properties 2 required
NotificationRecipient
string
cursor
string
Specific location in some collection.
CountPerType
object
Alert counters per type while grouping by severity as well.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

acronis-alerts-v1-openapi.json Raw ↑

Other APIs Acronis publishes across the network.

Acronis Resource and Policy Management API
Acronis Advanced Automation API
Acronis Event Manager API
Acronis Disaster Recovery Service API
Acronis Endpoint Detection and Response API
Acronis Vault Manager REST API
Acronis Activities API
Acronis Agent Updates API
Acronis Agents API
Acronis Authentication API
Acronis Clients API
Acronis Hardware Nodes API
Where this information came from

This is an independent, third-party profile of Acronis Alert Manager API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.