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 Acronis tenants and users, read protection alerts, and pull reports so agents can automate MSP-level Cyber Protect Cloud operations across customer accounts.

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:
"provision a new 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.

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

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

Use Cases

Patterns agents use Acronis Cyber Protect Cloud API 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

Why though Jentic?

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

Credential isolation

Acronis client credentials are stored encrypted in the Jentic vault. Jentic mints bearer tokens via /2/idp/token at execution time and injects the Authorization header, so raw client secrets never appear in agent context.

Intent-based discovery

Agents search by intent — for example, 'provision a new Acronis tenant' — and Jentic returns POST /2/tenants with its input schema and the implicit auth flow.

Time to first call

Direct integration: 2-3 days for OAuth-style token mint, partner scoping, and error handling. Through Jentic: under 1 hour for the first working tenant call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sophos SIEM API

Endpoint security platform with centralized alert visibility for MSPs.

Choose Sophos for an endpoint security focus with strong threat data. Choose Acronis Cyber Protect Cloud for integrated cybersecurity plus backup under a single MSP console.

Complementary

CrowdStrike Falcon API

Endpoint detection and response API that complements backup-centric Acronis deployments.

Use CrowdStrike for advanced EDR and threat hunting. Use Acronis Cyber Protect when backup and basic endpoint protection in a single MSP console is the priority.

Complementary

Okta API

Identity provider for federating users into Acronis tenants and managing MSP staff access.

Use Okta to manage staff identity and SSO. Use Acronis Cyber Protect Cloud for tenant and protection-side user provisioning.

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 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 at https://app.jentic.com/sign-up.

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.