Authenticate securely using OAuth2 or API keys, ensuring only approved apps can access Snapshots API endpoints and perform operations.
Authenticate with your Acronis Cloud credentials or service account, then grant Snapshots API the appropriate scopes to read locations and manage snapshots.
– GET /locations — Retrieve available locations. – Additional endpoints are available in the API docs and covered in the sections below.
Trigger by mapping Snapshots API location data to Acronis environments
Actions: fetch locations, create backups, monitor status
GET /locations
Key fields: id, name, region
Trigger on backup events to sync with Acronis Cloud Console
Actions: subscribe to events, push updates, reconcile state
POST /webhooks/events
Key fields: event_type, resource_id, timestamp
Trigger on a cadence to align data across systems
Actions: batch fetch, compare, resolve conflicts
GET /locations/batches
Key fields: batch_id, status, last_updated
Automate backup visibility without writing code using visual workflows and triggers
Centralized orchestration reduces manual steps and accelerates recovery times
Consistent data across platforms improves compliance and reporting
Definitions of common terms used when integrating APIs with cloud platforms, including endpoints, authentication, and data fields.
Verifying identity to allow access to Snapshots API and Acronis resources, typically via OAuth2 tokens or API keys.
A specific API route that performs an action or returns data, such as GET /locations.
A callback URL that receives real-time event data from Snapshots API to trigger actions in Acronis Cloud.
A grouped set of API calls executed together, often used for scheduled synchronization.
Use predictive analytics to forecast backup windows and optimize resource use within the Acronis environment.
Set up automated failover and test plans triggered by Snapshots API events.
Consolidate backup and recovery data from Snapshots API and Acronis into a single pane of glass.
Obtain OAuth2 tokens or API keys and grant the required scopes for location read access.
Set up the GET /locations endpoint and any needed webhooks to receive events from Snapshots API.
Run tests to confirm data synchronization and recovery workflows across systems.
Not at all. The integration is designed for no-code automation using visual workflows and built-in mapping tools. You can connect in minutes and start automating backups without writing code.
Most users start with API keys for quick setup, then migrate to OAuth2 for production environments with granular scopes and token lifecycles.
Yes. Use sandbox or a test location to validate the workflow before enabling production backups.
You can poll the API for status updates or subscribe to webhooks to receive real-time notifications of backup events.
Locations are exposed via GET /locations and can be extended with additional query parameters for filtering and pagination as needed.
Yes—grant the Snapshots API the saas/location.read permission and any other required scopes for your use case.
Developer docs, endpoint references, and authentication guides are available in the official Snapshots API docs and the Acronis Cloud integration portal.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
