Acronis Cyber Protect Cloud API

Name: Acronis Cyber Protect Cloud API API
Brand: Acronis Cyber Protect Cloud API
Availability: InStock

★ Only Publicly Available SpecSecurityThreat Detectionbearer13 EndpointsREST

For Agents

Provision tenants, manage users, review security alerts, and pull reports from Acronis Cyber Protect Cloud through a bearer-authenticated platform API.

Quickstart

Get started with Acronis Cyber Protect Cloud API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an acronis tenant"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Acronis Cyber Protect Cloud API API.

Issue platform access tokens from the IDP token endpoint for downstream calls

Provision and update tenants under a managed service provider account

Manage user accounts including creation, lookup, and updates

Review and triage cyber protection alerts across tenants

GET STARTED

Start building with Acronis Cyber Protect Cloud API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Acronis Cyber Protect Cloud API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Acronis Cyber Protect Cloud API, keeping it validated and agent-ready. The Acronis Cyber Protect Cloud API exposes platform management for managed service providers and IT teams running Acronis-backed cyber protection: tenant provisioning, user lifecycle, alert review, and reporting. It uses bearer token authentication issued through the /2/idp/token endpoint and operates on the cloud.acronis.com/api base. The endpoint surface is compact and tuned for partner-portal automation rather than backup-agent control.

Use Cases

Patterns agents use Acronis Cyber Protect Cloud API API for, with concrete tasks.

★ MSP Tenant Provisioning

Automate the creation of new customer tenants when a managed service provider onboards a client. The /2/tenants endpoint accepts POST requests to create tenants and GET requests with the tenantId path to read them back. Combined with /2/users, this lets the partner spin up a customer environment, attach administrators, and hand over access without clicking through the partner portal. Suited to MSPs onboarding tens of customers per month.

Create a new tenant called 'Acme Corp', then add an administrator user with email admin@acme.com under that tenant.

Alert Triage Automation

Pull alerts from Acronis Cyber Protect Cloud into a SIEM, ticketing system, or on-call workflow. The /2/alerts endpoint returns the alert list across the partner account so security teams can prioritise high-severity events without staying logged in to the Acronis console. This pattern fits MSPs and internal security operations that want a single pane of glass.

List all open alerts from /2/alerts and forward any with severity 'high' to the on-call ticketing queue.

Posture Reporting

Generate operational reports on backup, recovery, and protection posture for executive review or customer billing. The /2/reports endpoint surfaces reports built from the Acronis platform so partners can email weekly summaries, populate customer-facing dashboards, or feed compliance evidence packages. Replaces manual export from the partner console.

Fetch the latest protection posture report for tenant 'Acme Corp' and summarise backup success rate over the last 7 days.

AI Agent MSP Operations Copilot

Let an AI agent handle routine MSP operations on Acronis Cyber Protect Cloud — onboarding tenants, adding users, surfacing alerts, and pulling reports. Through Jentic the agent searches by intent, loads the right operation schema, and executes calls with credentials kept in the Jentic vault. This pattern fits MSP operations teams running a copilot for tier-one tasks.

Search Jentic for the Acronis tenant creation operation, load the schema, and provision a new tenant for 'Acme Corp' using a scoped Jentic credential.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for acronis cyber protect cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/2/idp/token

Issue an access token

GET

/2/tenants

List tenants

POST

/2/tenants

Create a new tenant

GET

/2/tenants/{tenantId}

Get a single tenant

GET

/2/users

List users

POST

/2/users

Create a user

GET

/2/alerts

List cyber protection alerts

GET

/2/reports

List operational reports

POST

/2/idp/token

Issue an access token

GET

/2/tenants

List tenants

POST

/2/tenants

Create a new tenant

GET

/2/tenants/{tenantId}

Get a single tenant

GET

/2/users

List users

POST

/2/users

Create a user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Acronis API client credentials and bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped, time-bound access token at execution — raw long-lived credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create acronis tenant') and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without browsing the partner-portal docs.

Time to first call

Direct Acronis integration: 2-4 days for IDP token flow, tenant onboarding logic, and alert/report polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Rubrik API

Enterprise data protection and backup management platform

Choose Rubrik for large enterprise backup deployments where the protection platform itself is Rubrik rather than Acronis.

Alternative

Acronis (acronis.com)

The same API surface accessible via the acronis.com hostname

Choose this when working from documentation that points at acronis.com rather than cloud.acronis.com — same operational surface, different hostname.

Complementary

Okta API

Identity provider for SSO into Acronis tenants and admin consoles

Use Okta alongside Acronis to provision and deprovision admin users with SSO, while Acronis owns tenant and protection posture.

FAQs

Specific to using Acronis Cyber Protect Cloud API API through Jentic.

Why is there no official OpenAPI spec for Acronis Cyber Protect Cloud API?

Acronis does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Acronis Cyber Protect Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Acronis Cyber Protect Cloud API use?

The API uses HTTP bearer tokens. Tokens are issued by POST /2/idp/token and then passed in the Authorization header on all platform calls. Through Jentic, the client secret used to mint tokens is held in the Jentic vault and never enters the agent's context.

Can I provision new tenants through the Acronis Cyber Protect Cloud API?

Yes. POST /2/tenants creates a new tenant under the partner account, and GET /2/tenants/{tenantId} reads it back. Pair with POST /2/users to attach an administrator and you have a complete onboarding flow.

What are the rate limits for the Acronis Cyber Protect Cloud API?

The spec does not declare explicit rate limits. Acronis applies platform-level limits per partner; check the partner portal under your account for the current quota before running bulk tenant or report operations.

How do I list cyber protection alerts through Jentic?

Search Jentic with 'list acronis alerts', load the schema for GET /2/alerts, then execute. Install with pip install jentic and use client.search, client.load, and client.execute. The Jentic vault holds the bearer credential.

Does this API control backup agents directly?

No. This spec covers platform management — tenants, users, alerts, and reports. It is not the agent-side API for triggering individual backup or recovery jobs on a protected workload.