To securely connect, generate and manage access tokens with the appropriate scopes for creating and reading data within the Social Media API. Use OAuth or API keys as supported by the integration.
Grant the Acronis Cyber Protect Cloud app permission to access your GHL data, configure API keys or OAuth credentials, and run a connectivity test to confirm a healthy connection.
Endpoint list: POST /bulk-disable-saas/:companyId; GET /snapshots; GET /social-media-posting/:locationId/accounts; DELETE /social-media-posting/:locationId/accounts/:id; GET /social-media-posting/:locationId/csv; POST /social-media-posting/:locationId/csv; POST /social-media-posting/:locationId/set-accounts; GET /social-media-posting/:locationId/csv/:id; DELETE /social-media-posting/:locationId/csv/:id; PATCH /social-media-posting/:locationId/csv/:id; POST /social-media-posting/:locationId/posts/bulk-delete; DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId; snapshots.readonly; socialplanner/account.readonly; socialplanner/account.write; socialplanner/csv.readonly
Trigger: a new post is created in Social Media API, which automatically posts to all connected Acronis social accounts.
Actions: publish the post across linked accounts, update status, and log results for audit.
POST /social-media-posting/:locationId/posts/bulk-delete
locationId, postId, accountId, locationId
Trigger: a CSV file is uploaded to the system, initiating account provisioning and scheduled posts.
Actions: parse CSV, create accounts, map fields, and schedule posts for each account.
POST /social-media-posting/:locationId/csv
locationId, csvId, accountId, postId
Trigger: new snapshots or analytic events update dashboards and influence posting decisions.
Actions: fetch snapshots, refresh dashboards, adjust posting times and content strategy.
GET /snapshots
locationId, snapshotId, accountId
Save time and reduce manual steps with automated workflows that handle posting, CSV processing, and account management.
Access and manage accounts, CSVs, and posts from a single unified interface without custom coding.
Scale your operations with auditable actions, logs, and snapshot-based insights for compliance.
This glossary defines API concepts used in this integration: endpoints (URL paths that perform actions), CSV files (data imports), posts (social updates), and accounts (connected profiles).
A specific URL path that performs an action in the Social Media API.
A file format used to batch-upload accounts or data for processing.
A social update sent to one or more connected accounts.
A social profile linked to a location in your GHL workspace.
Automatically publish the same post to every connected social profile when a trigger occurs, reducing manual work.
Use a CSV to batch-create accounts and schedule the initial posts to accelerate onboarding.
Pull snapshots to refine posting times and content strategy for better engagement.
Obtain OAuth tokens and grant permissions for both systems, then verify connectivity.
Select the needed endpoints and set required parameters such as locationId and companyId.
Run test flows and confirm data moves correctly before going live.
No coding is required to connect when using the built-in endpoints and no-code workflows. You can configure triggers, actions, and mappings in the UI. For advanced flows, you can extend logic with lightweight scripts if supported.
Yes. You can automate post scheduling across connected accounts by triggering a publish action or a bulk posting job. Schedule, update, and requeue posts from a single workflow.
Accounts are managed by uploading or mapping via CSV files, then syncing with the location context. Use the CSV endpoint to import and link each account to a location.
Security relies on OAuth tokens or API keys, with proper scopes. Store credentials securely and rotate keys regularly. Implement token refresh and error handling to maintain a stable connection.
Most integrations require endpoints for accounts, CSVs, and posts, plus a location context. Review the available endpoints above and enable only what you need.
Yes. Use a sandbox or test environment to validate flows with sample data before applying changes to live accounts.
Implement retries with exponential backoff, timeout limits, and robust logging to detect and recover from transient errors.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
