Use OAuth 2.0 to grant Rankr access to Snapshots API data. You’ll obtain a client ID and secret and configure a redirect URL for secure token exchange.
Store and rotate your API keys securely within Rankr’s settings; never expose keys in logs or public folders.
– GET /locations — fetches all locations used by 97Display panels – Note: Additional endpoints may be available for future expansions; this page focuses on location data access.
Triggered when Rankr needs the latest location data to populate 97Display panels.
Actions: Retrieve location records and map fields (id, name, address) to Rankr’s data model.
GET /locations
id, name, address, timezone
Triggered when a location is updated in GHL.
Actions: Update Rankr location record to reflect changes.
GET /locations/{id}
id, updated_at
Trigger: nightly scheduled run.
Actions: Create or update multiple location entries in Rankr.
GET /locations?limit=100
bulk_id, timestamp
Automate data flow without writing a line of code.
Keep data fresh with scheduled syncs and automatic retries.
View all location data in a unified Rankr dashboard for quick insights.
Key elements include endpoints, triggers, actions, method paths, and fields.
A URL path exposed by the API to perform a specific operation.
An event that starts an automation in Rankr when data changes.
The process of proving identity to access API data.
Linking API data fields to Rankr fields for accurate data flow.
Embed real-time location data in Rankr dashboards for instant insights.
Trigger automations the moment a location changes to keep actions timely.
Schedule nightly imports to maintain up-to-date location data in Rankr.
Obtain OAuth tokens and set the proper scopes for location.read.
Align API response fields with Rankr’s data model and map to 97Display fields.
Test the connection, verify data transfer, then enable automation in production.
No coding is required to connect Rankr with Snapshots API using the app connector. The integration uses OAuth 2.0 authentication and point-and-click mapping to align fields between Snapshots API and Rankr. Now you can automate data flow without writing code. If you need more advanced logic later, you can combine this with webhooks or additional endpoints to extend capabilities without touching core setup.
GET /locations returns a list of location objects such as id, name, address, and timezone. For example, a location with id 101, name HQ, and its address will be retrieved. In Rankr, map these fields to your 97Display data model to populate dashboards. You can also filter results and limit the batch as needed. The integration requires the location.read scope.
Sync frequency can be scheduled (nightly) or triggered by your workflow when needed. Real-time updates are possible if you configure webhooks or event-driven triggers. The default approach balances reliability and API usage limits.
Two-way updates are typically limited in this setup. Read access to Snapshots API is straightforward, but pushing edits back to GHL may require additional workflows or API capabilities beyond the standard connection. Check your API plan for write permissions.
Required permissions include the location.read scope and standard OAuth credentials. Ensure you have granted access to the Snapshots API and that Rankr is allowed to read location data. Maintain secure storage of tokens and rotate them periodically.
To revoke access, disconnect the app in GHL’s connected apps or revoke the OAuth token in Rankr. After revocation, re-authenticate if you want to re-establish the connection. Be sure to remove any stored credentials from both sides.
Integration logs are available in Rankr’s Integration Logs section and in the GHL app audit trail. Review timestamps, request payloads, and response codes to diagnose issues or verify successful data transfers.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
