Authenticate requests to the Users API with your API key or OAuth credentials. Include the access token in your request headers and scope the call to socialplanner tagged endpoints.
Rankr uses OAuth 2.0 or an API key depending on your setup. Keep credentials secure and rotate keys regularly.
Endpoint 1: GET /social-media-posting/:locationId/tags – retrieve tags for a location. Endpoint 2: POST /social-media-posting/:locationId/tags/details – submit or update tag details. Endpoint 3: socialplanner/statistics.readonly – read aggregated statistics. Endpoint 4: POST /social-media-posting/statistics – post new statistics. Endpoint 5-17: not defined in this page context.
Trigger when a new post is created to pull tags from the location and apply them to Rankr CRM.
Actions include retrieving tags, creating or updating Rankr tags, and syncing tag details.
GET /social-media-posting/:locationId/tags
locationId, tagId, name
When tag details are updated on the GHL side, push changes to Rankr
Actions include posting details to the details endpoint and updating Rankr records
POST /social-media-posting/:locationId/tags/details
locationId, tagDetails
Schedule or event driven sync of statistics from GHL to Rankr
Actions include posting to the statistics endpoint and updating dashboards in Rankr
POST /social-media-posting/statistics
scope, metric, timestamp
Rapid setup without custom code using visual builders and webhooks.
Easier maintenance with centralized configuration and clear endpoints.
Secure credential management and role based access controls.
Common terms and processes used when integrating the Users API with Rankr for CRM workflows.
An API is a set of rules for how software components communicate with each other.
OAuth 2.0 is an authorization framework that enables secure access delegation.
An API endpoint is a specific URL where a client can request data or perform an action.
A webhook is a callback URL that gets invoked when a specific event occurs.
Automatically import and apply tags from posts to Rankr CRM using endpoints 1 and 2.
Pull stats updates after posts go live to drive analytics in Rankr.
Implement retries and helpful error messages to keep CRM syncing smooth.
Register your Rankr app in the GHL developer portal and obtain API keys.
Set scope to socialplanner/tag.readonly and related permissions for reading tags.
Run test requests to verify authentication and endpoint access.
Authentication should use API keys or OAuth 2.0 depending on your setup. Include the access token in request headers and scope calls to the correct endpoints. This ensures secure access and auditability. In tests, simulate both success and failure scenarios to validate the flow.
The essential endpoints for tag management are the get tags endpoint and the tags details endpoint. These allow reading and updating tag data and align with your CRM records.
Store credentials securely using a secret manager or environment variables. Rotate keys periodically and restrict access to sensitive data. Use least privilege access for applications.
Yes. No code tools can connect to the Users API via webhooks and prebuilt connectors. Use the sample endpoints and verify data through test requests.
Implement retries with exponential backoff, handle rate limits, and provide clear error messages so your Rankr dashboards remain accurate. Implement observability where possible.
Map fields between the Users API data model and Rankr CRM fields. Establish a mapping table and use transform steps in your integration layer to normalize data.
Consult the endpoint references in this guide for example requests, including endpoint paths, methods and required parameters.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
