Authenticate by issuing an API key or OAuth token for Users API and store it securely in Rankr. Every request should include your token in the Authorization header.
In Rankr, open Settings > Integrations, select the Users API connection, and paste your credentials. Run a test to confirm connectivity.
– GET /social-media-posting/:locationId/tags — Retrieve tags for a location – POST /social-media-posting/:locationId/tags/details — Retrieve or update tag details – socialplanner/statistics.readonly — Read-only statistics data – POST /social-media-posting/statistics — Submit statistics payload to update analytics
Trigger: when new tags are created or updated in Rankr, fetch tag details from Users API.
Actions: retrieve and map locationId with tags, then push updates back to Rankr.
GET /social-media-posting/:locationId/tags
locationId, tags
Trigger: on-demand pull of analytics data from Users API.
Actions: POST /social-media-posting/statistics with locationId and metrics to update Rankr dashboards.
POST /social-media-posting/statistics
locationId, metrics
Trigger: run a read-only statistics fetch when needed.
Actions: call GET /socialplanner/statistics.readonly and refresh Rankr dashboards.
GET /socialplanner/statistics.readonly
locationId
No-code automation lets teams build powerful workflows without writing code.
Unified dashboards and reporting across Rankr and the Users API.
Faster time-to-value with reusable, drag-and-drop integrations.
Definitions and explanations of API terms used in this guide and how they relate to Rankr and the Users API.
A specific URL combined with an HTTP method that performs an action on a resource within an API.
An event that starts a workflow or a sequence of actions in an automation platform.
A process to verify identity and grant access to a system.
The process of aligning data fields between different systems so data flows correctly.
Automatically pull engagement metrics from Users API and push to Rankr dashboards for stakeholders.
Notify teams when tag sentiments change significantly to adjust campaigns in real time.
Coordinate posting sequences across social channels via Rankr using the Users API data.
In Rankr, go to Settings > Integrations, choose Users API, and generate credentials.
Enter credentials, authenticate, and run a quick test call to verify access.
Create a workflow that uses endpoints to fetch tags and statistics, then push results to Rankr.
The GetScreenshot integration lets you pull tag data from a specific location in GHL and bring it into Rankr for reporting. It also supports updating tag details via the tags/details endpoint. This enables a unified view of tagging across platforms. No code is required to set up basic workflows, and you can extend them with additional actions as needed.
Endpoints available include retrieving tags (GET /social-media-posting/:locationId/tags), updating tag details (POST /social-media-posting/:locationId/tags/details), reading statistics (socialplanner/statistics.readonly), and posting statistics (POST /social-media-posting/statistics). Additional endpoints may be used as needed for your use case.
Authentication typically uses an API key or OAuth token for the Users API. Ensure the token has the required scope (for example, socialplanner/tag.readonly) and that you pass it in the Authorization header with each request.
No traditional coding is required thanks to Rankr’s integration builder. You can connect accounts, map fields, and configure triggers and actions using a visual workflow designer.
Yes. The Users API provides a statistics endpoint (statistics.readonly) and a statistics submit endpoint (statistics) that can be used to pull or push analytics data into Rankr for reporting and dashboards.
Field mapping typically involves pairing locationId with the appropriate resource identifiers (tags, metrics) and ensuring data types align between GHL and Rankr so data flows correctly.
For more documentation, consult the official API docs and the Rankr integration guide within your dashboard, plus any developer portals provided by the GHL API and the app connector.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
