To authorize Your App to access the Social Media API, obtain an API key with the scope saas/company.write and secure your requests with token-based authentication. This ensures controlled access to publishing, CSV handling, and account management features.
Your App should use standard OAuth 2.0 or API key-based authentication to connect to the Social Media API, and should request the saas/company.write scope to perform write operations.
1) POST /bulk-disable-saas/:companyId; 2) snapshots.readonly; 3) GET /snapshots; 4) socialplanner/account.readonly; 5) GET /social-media-posting/:locationId/accounts; 6) socialplanner/account.write; 7) DELETE /social-media-posting/:locationId/accounts/:id; 8) socialplanner/csv.readonly; 9) GET /social-media-posting/:locationId/csv; 10) GET /social-media-posting/:locationId/csv/:id; 11) socialplanner/csv.write; 12) POST /social-media-posting/:locationId/csv; 13) POST /social-media-posting/:locationId/set-accounts; 14) DELETE /social-media-posting/:locationId/csv/:id; 15) PATCH /social-media-posting/:locationId/csv/:id; 16) POST /social-media-posting/:locationId/posts/bulk-delete; 17) DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId
Trigger: When new content is ready in Your App, push to Social Media API to post or schedule via /social-media-posting/:locationId endpoints.
Actions: Publish posts (POST /social-media-posting/:locationId/posts/bulk-delete as needed), upload and manage CSVs (POST /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv; DELETE /social-media-posting/:locationId/csv/:id; PATCH /social-media-posting/:locationId/csv/:id), and link accounts (POST /social-media-posting/:locationId/set-accounts).
Method paths: /social-media-posting/:locationId/csv, /social-media-posting/:locationId/csv/:id, /social-media-posting/:locationId/accounts, and /social-media-posting/:locationId/posts/bulk-delete.
Key fields: locationId, csvId, postId, accountId.
Trigger: When a new CSV is prepared in Your App, upload via POST /social-media-posting/:locationId/csv and schedule posts accordingly.
Actions: Upload CSV (POST /social-media-posting/:locationId/csv), view CSVs (GET /social-media-posting/:locationId/csv), manage specific CSVs (GET /social-media-posting/:locationId/csv/:id; DELETE /social-media-posting/:locationId/csv/:id; PATCH /social-media-posting/:locationId/csv/:id), and attach accounts (POST /social-media-posting/:locationId/set-accounts).
Paths: POST /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv/:id; DELETE /social-media-posting/:locationId/csv/:id; PATCH /social-media-posting/:locationId/csv/:id.
Fields: locationId, csvId, id.
Trigger: After content is prepared, push posts directly to social accounts and optionally remove outdated posts in bulk.
Actions: Use posting endpoints to publish (POST /social-media-posting/:locationId/accounts and related endpoints), manage accounts, and perform bulk deletions via POST /social-media-posting/:locationId/posts/bulk-delete.
Paths: /social-media-posting/:locationId/accounts, /social-media-posting/:locationId/accounts/:id, /social-media-posting/:locationId/posts/bulk-delete.
Fields: locationId, id, accountId, postId.
Automate repetitive publishing tasks without writing code, speeding up campaigns and ensuring consistency across channels.
Centralized data and dashboards let you monitor performance from a single place, reducing context switching.
Secure, permission-based access with token scopes keeps your data safe while enabling seamless automation.
Key elements include API endpoints, authentication flow, CSV handling, location-based accounts, and the mapping of triggers to actions across your app and the Social Media API.
A specific URL and HTTP method used to perform an action with the Social Media API.
The process of proving identity to obtain an access token and grant permissions for API usage.
Comma-separated values format used to bulk import or export data such as posts or accounts.
A unique identifier for a social location within the GHL setup used by endpoints to scope actions.
Automatically pull approved content from Your App into a CSV and upload it to Social Media API to schedule posts across locations.
Use templates for branding consistency and periodically bulk-delete outdated posts to keep accounts tidy.
Combine snapshot data with CSV and posting metrics to create live dashboards for performance insights.
Register Your App and obtain an API key with scope saas/company.write to enable write access to accounts, CSVs, and posts.
Map triggers in Your App to endpoints like POST /social-media-posting/:locationId/csv and GET /social-media-posting/:locationId/csv/:id to automate CSV workflows.
Create automation rules to publish posts, manage accounts, and clean up old data using the bulk-delete endpoints.
The Social Media API lets you programmatically manage posting, CSV workflows, and accounts for Your App. It provides structured endpoints to publish content, import and export data via CSV, and oversee account settings across locations. This API enables automation at scale with secure access.
To authenticate, obtain an API key with the saas/company.write scope and include the token in each request. Use standard OAuth 2.0 flows or API key headers as appropriate for your integration. Always rotate tokens and enforce least privilege access.
CSV-related endpoints include POST /social-media-posting/:locationId/csv, GET /social-media-posting/:locationId/csv, GET /social-media-posting/:locationId/csv/:id, PATCH /social-media-posting/:locationId/csv/:id, and DELETE /social-media-posting/:locationId/csv/:id. These allow bulk uploads, updates, and cleanup of CSV data tied to specific locations.
Yes. You can bulk delete posts via POST /social-media-posting/:locationId/posts/bulk-delete and purge CSV-derived posts or outdated entries using the related delete endpoints. Ensure you have the proper locationId and IDs for targeted deletions.
The required scope for write operations is saas/company.write. This scope governs creating, updating, and deleting resources such as accounts, CSVs, and posts. Use the principle of least privilege when requesting scopes for your app.
Test endpoints in a staging environment by using sample location IDs and sandbox CSV data. Verify responses, status codes, and data integrity before moving to production. Use mock data to replicate real-world workflows.
Location-based accounts are managed via endpoints like GET /social-media-posting/:locationId/accounts and POST /social-media-posting/:locationId/set-accounts. This supports multi-location setups and role-based access control for teams.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
