Acronis Cyber Protect Cloud API
Agent-ready OpenAPI document · curated by JenticSecurityThreat Detectionbearer13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision Acronis tenants and users, read protection alerts, and pull reports so agents can automate MSP-level Cyber Protect Cloud operations across customer accounts.
Use for: I want to provision a new client tenant for an MSP customer, Create a new user within an existing Acronis tenant, List all active alerts for a customer tenant, Update a user's role inside a tenant
Not supported: Does not handle backup agent installation, recovery jobs, or per-machine protection plan editing - use for tenant management, user management, alerts, and reports on Acronis Cyber Protect Cloud only.
Jentic publishes the only available OpenAPI specification for Acronis Cyber Protect Cloud API, keeping it validated and agent-ready. The Cyber Protect Cloud API exposes platform management for managed service providers and enterprise tenants - tenant management, user management, alerts, and reporting - through 13 endpoints under cloud.acronis.com/api. Authentication is bearer token, obtained via POST /2/idp/token. The API is used by MSPs and security teams to provision client tenants, manage user access, and read protection alerts programmatically.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Facronis.com%2Facronis-cyber-protect-cloud-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Facronis.com%2Facronis-cyber-protect-cloud-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Provision a new client tenant under an MSP partner account
Update or delete an existing tenant by tenantId
Create users within a tenant and update their roles
Read active protection alerts surfaced by Acronis Cyber Protect
Pull tenant-level reports for billing and protection coverage
Obtain bearer tokens via the identity provider token endpoint
Use Cases
Patterns agents use Acronis Cyber Protect Cloud API for, with concrete tasks.
★ MSP Onboarding Automation
An MSP onboarding tool calls POST /2/tenants to create a new client tenant when a sales deal closes, then POST /2/users to provision admin users for the customer. The same tool sets baseline protection settings via downstream Acronis APIs. New customers are live in Cyber Protect Cloud within minutes instead of hours of manual setup.
Create a new tenant under the MSP partner id with the customer name and primary admin user, then return both ids
Centralized Alert Triage Across Customers
A SOC dashboard pulls /2/alerts across all customer tenants every minute and routes high-severity alerts into a ticketing system. Analysts triage from one console rather than logging into each tenant's portal. Bearer tokens scoped to the partner read across the customer fleet, and reports endpoints back the dashboard's coverage metrics.
List alerts across all child tenants in the last 5 minutes, filter to severity high or critical, and return them with tenantId
Tenant Lifecycle Management on Customer Churn
When a customer churns, an offboarding workflow uses DELETE /2/tenants/{tenantId} to remove the tenant after data retention has been honored. PUT /2/tenants/{tenantId} downgrades the tier earlier in the cycle. The lifecycle is automated rather than tracked in spreadsheets, which prevents stale tenants from accumulating in billing reports.
Find the tenantId for a churning customer, downgrade its tier with PUT /2/tenants/{tenantId}, and schedule the DELETE for after the retention window
Agent-Driven MSP Operations via Jentic
An MSP-side AI assistant uses the Cyber Protect Cloud API through Jentic to handle routine operations: provisioning tenants, resetting users, fetching alert summaries. The agent searches Jentic for the right operation, the bearer token flow is brokered, and credentials never enter the agent's context.
Through Jentic, search 'provision a new Acronis tenant', load POST /2/tenants, and create the tenant for a named customer
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
Obtain a bearer access token
GET
/2/tenants
List tenants
POST
/2/tenants
Create a new tenant
GET
/2/tenants/{tenantId}
Retrieve a specific tenant
PUT
/2/tenants/{tenantId}
Update a tenant
DELETE
/2/tenants/{tenantId}
Delete a tenant
GET
/2/users
List users in scope
POST
/2/users
Create a user inside a tenant
POST
/2/idp/token
Obtain a bearer access token
GET
/2/tenants
List tenants
POST
/2/tenants
Create a new tenant
GET
/2/tenants/{tenantId}
Retrieve a specific tenant
PUT
/2/tenants/{tenantId}
Update a tenant
DELETE
/2/tenants/{tenantId}
Delete a tenant
GET
/2/users
List users in scope
POST
/2/users
Create a user inside a tenant
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Acronis Cyber Protect Cloud API by hand means minting bearer tokens via /2/idp/token, refreshing them, and attaching the Authorization header across tenant and user endpoints. 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 and update that tenant and nothing else. You choose the operations it may call, so tenant deletion is not included unless you add it.
Credential isolation
Your Acronis client credentials are stored once, encrypted, by your own Jentic One instance, which mints bearer tokens and injects the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'provision a new Acronis tenant', and Jentic returns POST /2/tenants with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 a single canonical OpenAPI specification for the Cyber Protect Cloud platform management surface. 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?
Bearer token authentication. Obtain a token via POST /2/idp/token using the partner's client credentials, then pass it on each request as Authorization: Bearer <token>. Through Jentic, the client credentials are stored encrypted and tokens are minted at execution time.
Can I provision tenants and users with this API?
Yes. POST /2/tenants creates a tenant, PUT /2/tenants/{tenantId} updates it, and DELETE /2/tenants/{tenantId} removes it. POST /2/users creates a user inside a tenant. The 13-endpoint surface focuses on tenant and user lifecycle plus alerts and reports.
What are the rate limits for the Cyber Protect Cloud API?
The OpenAPI spec does not document explicit rate limits. Acronis applies per-partner limits documented in their developer portal. Implement exponential backoff on HTTP 429 and batch reads where possible to avoid hitting per-minute caps during fleet-wide alert scans.
How do I provision a new tenant through Jentic?
Run pip install jentic, then search 'provision a new Acronis tenant'. Jentic returns POST /2/tenants with its input schema, you supply the tenant name and partner id, and execute. The bearer token mint via /2/idp/token is brokered by the Jentic execution layer.
Does this API include agent management for endpoints?
The endpoints in this spec focus on tenant management, user management, alerts, and reports - that is the platform layer. Backup agent installation, recovery operations, and protection plan editing are part of broader Acronis APIs and are not present in this OpenAPI cut.
Can I limit what my agent is allowed to do with the Acronis Cyber Protect Cloud API?
Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use with the Acronis Cyber Protect Cloud API. Since Acronis puts the tenant id in the URL path, such as /2/tenants/{tenantId}, you can pin the agent to a single tenant so it reads and updates that tenant and nothing else. You choose the exact operations it may call, so destructive ones like DELETE /2/tenants/{tenantId} are excluded unless you add them, and you can allow only reads such as GET /2/alerts while withholding POST /2/tenants or POST /2/users.
GET STARTED