Connect Acronis Cyber Protect Cloud
This guide explains how to create the Acronis API client that Alerion's connection form asks for (Settings → Connectors → Acronis Cyber Protect). Alerion reads backup status read-only.
Prerequisites
- Administrator access to the Acronis Cyber Protect Cloud management portal of the end customer. The official page does not state which role is needed to create an API client: if Settings → API clients is missing, ask the customer's Acronis administrator.
- An Alerion plan that includes the connector (Business or above).
Alerion rule: end customer, never partner level
Create the API client in the end customer's tenant, never at partner level. This is an
Alerion rule, not an Acronis one: a partner-level API client would also see the partner's
other customers, and Alerion refuses it at connection time ("This key was created at
partner level"). Alerion accepts clients of kind customer or unit.
Acronis' official page does not say which tenant the new client belongs to; the developer documentation only says the token allows operating in the API client's tenant "and its sub-tenants". Before creating the client, make sure you are working in the end customer's tenant.
Create the API client step by step
Steps taken from the official "Creating an API client" page (see Sources):
- In the Acronis management portal, open Settings → API clients, then click Create API client.
- Enter a name, for example
Alerion (read). - Click Next. The client is created with Active status.
- Immediately copy and save the ID, the secret value and the data center URL. The secret is shown only once; if lost it cannot be retrieved, but it can be reset to generate a new one.
- Click Done.
Exact menu names may vary with the portal version (the official page consulted is for version 25.09).
Value of each Alerion form field
| Alerion field | Value to enter |
|---|---|
| Data center URL | The URL displayed with the API client, for example https://eu2-cloud.acronis.com (example from Acronis' developer documentation). |
| API client identifier | The client ID shown at creation. |
| API client secret | The secret value, shown only once. |
Alerion encrypts the secret, never displays it again and never writes it to logs.
Verification
When you submit the form, Alerion checks, before storing anything: that the token is accepted, the API client's tenant and kind (end customer only), then that it can read protection statuses. If any step fails, nothing is saved. Once connected, the connection page shows the date of the last synchronisation.
Common errors
- "Acronis refused the identifier or the secret": first check that the data center URL is the one displayed with the API client (a wrong data center causes an HTTP 401 refusal), then the secret. If the secret is lost, reset it in the Acronis portal.
- "This key was created at partner level": recreate the API client in the end customer's tenant.
- "Alerion could not verify these credentials": the provider did not answer; try again in a moment. Nothing was saved.
Sources
- Acronis, "Creating an API client": https://www.acronis.com/en-us/support/documentation/AcronisCyberCloud/creating-api-client.html
- Acronis Developer, "Authenticating to the platform" (ID, secret and data center URL; token valid in the client's tenant and its sub-tenants): https://developer.acronis.com/doc/account-management/v2/guide/getting-started/authenticating.html