Authorize SwagUp to access your GHL data using OAuth 2.0 or API keys. Request only the minimum scopes needed (tags and statistics) and keep credentials secure.
SwagUp authenticates with the GHL Users API via OAuth tokens and API keys. Treat tokens like passwords and rotate them periodically.
GET /social-media-posting/:locationId/tags — fetch tags for a location; POST /social-media-posting/:locationId/tags/details — retrieve detailed tag data; GET socialplanner/statistics.readonly — view analytics; POST /social-media-posting/statistics — submit posting statistics
Trigger: When a new post is prepared in SwagUp, pull current tags from GHL.
Actions: GET /social-media-posting/:locationId/tags to fetch tags; POST /social-media-posting/:locationId/tags/details to retrieve tag metadata.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName
Trigger: On-demand analytics refresh in SwagUp
Actions: GET socialplanner/statistics.readonly; POST /social-medIa-posting/statistics to push metrics
GET socialplanner/statistics.readonly
locationId, dateRange, metrics
Trigger: When SwagUp schedules a post, sync tags and update stats in GHL
Actions: POST /social-media-posting/statistics to update tag stats; GET /social-media-posting/:locationId/tags to verify tags
POST /social-media-posting/statistics
locationId, postId, tagIds
No custom development required—build powerful automation with point-and-click configuration.
Faster go-to-market by linking tags and analytics without writing code.
Easily deploy repeatable workflows across campaigns and locations.
A quick glossary of terms and processes used in the SwagUp–GHL connection, to help non-technical users.
Application Programming Interface: a set of rules that lets apps talk to each other, like SwagUp and the GHL Users API.
A specific path in an API that performs an action, such as fetching posts or tags.
The process of proving identity and permissions to access the GHL API from SwagUp.
A lightweight HTTP callback that notifies SwagUp of events in GHL in real time.
Set up a weekly digest that collects tag counts, post metrics, and audience insights from GHL and delivers them to your team in SwagUp.
Automatically tag content in SwagUp based on sentiment and engagement metrics pulled from GHL statistics.
Create a centralized dashboard in SwagUp that visualizes tags, performance, and optimization opportunities.
In GHL, register your application and generate a client ID and client secret, then authorize SwagUp to access the Users API.
Add the socialplanner and relevant scopes to your app and set the redirect URI to SwagUp’s callback endpoint.
Run a test request to ensure SwagUp can access the Users API data and that tags and statistics flow correctly.
You authenticate SwagUp to access your GHL data using OAuth 2.0 or API keys. SwagUp will request the minimum scopes required to read social planner tags and statistics. You can revoke access at any time from your GHL account.
The essential endpoints include GET /social-media-posting/:locationId/tags, POST /social-media-posting/:locationId/tags/details, GET socialplanner/statistics.readonly, and POST /social-media-posting/statistics. These endpoints enable fetching tags, tag details, and posting statistics.
You do not need to write code to set up this integration. The platform uses no-code configuration to connect SwagUp with the GHL Users API.
SwagUp will need read-only access to the social planner tags and statistics.
Statistics update frequency depends on the configuration, but typical setups refresh daily or on-demand when triggered.
Yes. You can configure which tags and metrics SwagUp pulls and displays, and adjust mappings.
You can monitor the status in SwagUp’s connection panel and in GHL’s connected apps dashboard.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
