Acronis Cyber Protect Cloud API

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.