Cloud Acronis Acronis Cyber Protect Cloud API

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

★ Only Publicly Available OpenAPI DocumentSecurityThreat Detectionbearer13 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Acronis Cyber Protect Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acronis Cyber Protect Cloud API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Acronis Cyber Protect Cloud 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

GET STARTED

Start building with Acronis Cyber Protect Cloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Acronis Cyber Protect Cloud 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 your Jentic One instance. 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 Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Acronis Cyber Protect Cloud 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 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.

Cloud Acronis Acronis Cyber Protect Cloud API

Connect the Acronis Cyber Protect Cloud API to your agent

Capabilities

Start building with Acronis Cyber Protect Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs