canonical: https://jentic.com/apis/cloud.acronis.com/acronis

# Cloud Acronis Acronis Cyber Protect Cloud API

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.

## For AI agents

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

## Scope

Does not control individual backup jobs, ransomware remediation, or endpoint protection agents - use for Acronis platform tenant, user, alert, and report management only.

## Capabilities

- 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
- Pull operational reports for backup, recovery, and protection posture

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance. This pattern fits MSP operations teams running a copilot for tier-one tasks.

Example prompt: 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

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

## Key resources

- **Authentication** — Issue platform access tokens via the IDP token endpoint
- **Tenants** — Create, read, and manage tenant accounts under a partner
- **Users** — Create, read, and manage user accounts within tenants
- **Alerts** — List and review cyber protection alerts across the partner
- **Reports** — Retrieve operational and protection posture reports

## Why Jentic

- **Setup:** Wiring Acronis Cyber Protect Cloud by hand means exchanging client credentials for a bearer token, refreshing it before expiry, mapping its tenant, user, alert, and report endpoints, and handling retries yourself against cloud.acronis.com/api. Through Jentic you install once, import the Acronis Cyber Protect Cloud API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Acronis puts the tenant id in the URL path (/2/tenants/{tenantId}), so a rule can pin your agent to one tenant: it can read that tenant and nothing else. You choose the operations it may call, so creating tenants or users are not included unless you add them.
- **Credential handling:** Your Acronis client credentials are stored once, encrypted, by your own Jentic One instance, which exchanges them for a scoped, time-bound token injected at execution time. The raw long-lived credentials never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an 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.

## Related APIs

- **Rubrik API** — Enterprise data protection and backup management platform
- **Acronis (acronis.com)** — The same API surface accessible via the acronis.com hostname
- **Okta API** — Identity provider for SSO into Acronis tenants and admin consoles

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance 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 One instance 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.

### Can I limit what my agent is allowed to do with the Acronis Cyber Protect Cloud API?

Yes. Jentic One runs self-hosted, so your own rules decide which Acronis operations and credentials the agent may use. Because Acronis carries the tenant id in the URL path (/2/tenants/{tenantId}), you can pin the agent to a single tenant so it reads that tenant and nothing else, and you choose exactly which operations it may call. If you only grant GET /2/alerts and GET /2/reports, the agent can review alerts and pull reports but cannot create tenants via POST /2/tenants or add users via POST /2/users unless you allow those too.