GHL’s Users API uses token based authentication with the required scope socialplanner/tag.readonly. Include the access token in the Authorization header for each request.
Vitally authenticates to the GHL API using OAuth 2.0 or API keys. Store tokens securely and rotate them regularly.
Endpoint 1: GET /social-media-posting/:locationId/tags fetches location tags. Endpoint 2: POST /social-media-posting/:locationId/tags/details retrieves tag details. Endpoint 3: socialplanner/statistics.readonly returns statistics. Endpoint 4: POST /social-media-posting/statistics submits statistics data.
Trigger: When a location’s tags are updated or requested to synchronize.
Actions: Retrieve tags and map them to Vitally fields for dashboards and reports.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName, timestamp
Trigger: Request details when depth is needed for a tag.
Actions: Pull tag details into Vitally and link to campaigns and tags.
POST /social-media-posting/:locationId/tags/details
locationId, tagId, details, status
Trigger: Periodic statistics pull to refresh insights.
Actions: Import aggregated metrics into Vitally dashboards for reporting.
socialplanner/statistics.readonly
totalPosts, engagement, date, locationId
Rapid setup with no coding required to connect Vitally to the Users API.
Automate data flow between Vitally and the Users API to keep insights up to date.
Accessible dashboards and reports without writing integration code.
A quick glossary of core terms and how they relate in this integration.
Definition: A method for granting access to resources via tokens with permissions controls.
Definition: A specific URL that exposes a function in the API.
Definition: A string used to authenticate and authorize API requests.
Definition: The data sent in a request or received in a response.
Automatically pull tags when new posts are created and sync them to Vitally for real-time tagging.
Use aggregated statistics to trigger Vitally-based campaigns or reports.
Automate tag curation and enrichment to improve targeting and insights.
Obtain an OAuth token or API key with the correct scope socialplanner/tag.readonly to access tags and stats.
Configure the app to request access to the Users API and approve permissions.
Run test calls to endpoints 1–3 and confirm data maps to Vitally.
With the Users API you can fetch tags for a location, pull tag details, and read statistics. Endpoint 1 returns tags for a given locationId. Endpoint 2 retrieves details for a specific tag, useful for enrichment in Vitally. The second paragraph: You can also read commonly requested metrics via socialplanner/statistics.readonly to surface dashboards in Vitally.
No code is required to get started using a connector like Zapier’s App Connector or Rankr templates. You can configure triggers and actions without writing code.
Requests are authenticated with tokens. Use the Authorization header Bearer
Tag data endpoints allow listing tags and retrieving tag details. They support locationId and tagId and map to Vitally fields.
Statistics refresh depends on your schedule or manual sync. Endpoint3 provides readonly metrics; you can pull data as often as needed within plan limits.
Yes. Payloads are JSON; you can customize fields and mapping between GHL and Vitally while respecting the API schema.
Docs are available in Rankr’s developer hub under the Users API and app connector sections; check endpoint notes for the latest details.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
