Acronis · Schema
AlertView
View of alert in responses.
CybersecurityData ProtectionEndpoint ManagementBackup and RecoveryDisaster RecoveryManaged Service ProvidersEndpoint Detection and ResponseCloud Storage
Properties
| Name | Type | Description |
|---|---|---|
| id | object | |
| type | string | |
| severity | string | Alert severity level. |
| affinity | string | Alert synchronization affinity (e.g., agent ID). |
| createdAt | string | A client-side date and time when alert was created. Equals to the `receivedAt` field if not set by client. |
| deletedAt | string | A date and time when the alert was dismissed. |
| details | object | Copy of context is merged to details. Null if details and context are empty. |
| receivedAt | string | A server-side date and time when the alert was received. |
| _source | string | An identifier of the alert producer. |
| _sourceTimeStamp | integer | |
| tenant | object | |
| updatedAt | string | A date and time when the alert has been activated, deleted or dismissed. |
| category | string | Alert category. |
| falsePositive | boolean | Specifies whether alert is false positive or not. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/acronis/main/json-schema/acronis-alert-view-schema.json",
"title": "AlertView",
"description": "View of alert in responses.",
"x-generated": "2026-10-27",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/acronis-alerts-api-openapi.yml#/components/schemas/AlertView",
"type": "object",
"required": [
"id",
"type",
"severity",
"createdAt",
"details",
"receivedAt",
"tenant",
"updatedAt",
"category"
],
"properties": {
"id": {
"$ref": "#/$defs/uuid"
},
"type": {
"type": "string"
},
"severity": {
"description": "Alert severity level.",
"enum": [
"ok",
"information",
"warning",
"error",
"critical"
],
"type": "string"
},
"affinity": {
"description": "Alert synchronization affinity (e.g., agent ID).",
"type": "string"
},
"createdAt": {
"description": "A client-side date and time when alert was created. Equals to the `receivedAt` field if not set by client.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)(\\.[0-9]+){0,1}(Z|(\\+|-)([01][0-9]|2[0-3]):([0-5][0-9]))$"
},
"deletedAt": {
"description": "A date and time when the alert was dismissed.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)(\\.[0-9]+){0,1}(Z|(\\+|-)([01][0-9]|2[0-3]):([0-5][0-9]))$"
},
"details": {
"description": "Copy of context is merged to details.\nNull if details and context are empty.\n",
"type": "object"
},
"receivedAt": {
"description": "A server-side date and time when the alert was received.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)(\\.[0-9]+){0,1}(Z|(\\+|-)([01][0-9]|2[0-3]):([0-5][0-9]))$"
},
"_source": {
"description": "An identifier of the alert producer.",
"type": "string"
},
"_sourceTimeStamp": {
"type": "integer",
"format": "int64"
},
"tenant": {
"type": "object",
"required": [
"id",
"locator"
],
"properties": {
"id": {
"description": "An identifier of the alert owner.",
"type": "string"
},
"locator": {
"description": "Ascending hierarchy of tenant IDs separated by '/'.",
"type": "string"
}
}
},
"updatedAt": {
"description": "A date and time when the alert has been activated, deleted or dismissed.",
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)(\\.[0-9]+){0,1}(Z|(\\+|-)([01][0-9]|2[0-3]):([0-5][0-9]))$"
},
"category": {
"description": "Alert category.",
"type": "string"
},
"falsePositive": {
"description": "Specifies whether alert is false positive or not.",
"type": "boolean"
}
},
"$defs": {
"uuid": {
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
}
}
}
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/acronis-alert-view"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.