The Users API uses OAuth 2.0 with the scope socialplanner/tag.readonly. Create a client in your GHL developer console and authorize Kenko to access tags and statistics securely.
Kenko stores and rotates tokens to call endpoints. Follow security best practices and keep credentials confidential.
GET /social-media-posting/:locationId/tags — retrieves tags for a given location.\nPOST /social-media-posting/:locationId/tags/details — fetches detailed information for a specific tag.\nsocialplanner/statistics.readonly — read-only statistics for insights.\nPOST /social-media-posting/statistics — submits post statistics for analysis.
Trigger: when a location is updated or a new post is published, pull tags for that location.
Actions: call GET tags, then call details for a selected tag.
GET /social-media-posting/:locationId/tags
locationId, tagId, name
Trigger: on demand or scheduled pull to refresh metrics.
Actions: GET socialplanner/statistics.readonly and POST /social-media-posting/statistics as needed.
GET socialplanner/statistics.readonly
totalPosts, engagement, reach
Trigger: after publishing content to assess impact.
Actions: POST /social-media-posting/statistics
POST /social-media-posting/statistics
locationId, timestamp, metrics
Automate tag retrieval and reporting with a low code workflow, no programming required
Consolidate tag data and statistics into a single automated process for dashboards
Secure access with scoped tokens and centralized credential management
This glossary defines common terms used in this guide, focusing on endpoints, authentication, and data fields you will encounter when wiring Kenko to the Users API.
A specific URL in the API that performs a defined action or returns data.
The process of proving identity to obtain access tokens for API calls.
A credential issued after authentication that authorizes API requests.
Permissions granted to an app to access specific resources or actions.
Schedule a daily pull of location tags and deliver a concise summary to your team via Kenko.
Combine engagement metrics with tag data to identify trends and notify stakeholders instantly.
Use tag data to score content performance and guide future posts for better results.
Register Kenko in the GHL developer portal and capture clientId and clientSecret.
Add the required endpoints and set scope to socialplanner/tag.readonly as needed.
Run tests, verify data flows, and deploy to production.
With the Users API you can access tags for a location, details for each tag, and read only statistics to inform your strategy. These capabilities enable tag driven insights and reporting without leaving Kenko. You can also pull location based stats to measure performance over time. This makes it easy to build dashboards and automated reports for teams.\nIn short,Kenko can fetch tags, pull tag details, and retrieve key statistics to power automation and decision making.
Yes, endpoints may have rate limits depending on your GHL plan. To maximize reliability, implement simple retry logic and batch requests when possible. Use the read only endpoints for frequent dashboards and reserve write operations for scheduled updates.
Use OAuth 2.0 with scoped tokens and rotate tokens regularly. Store tokens securely, avoid hard coding credentials, and use short lived access tokens with refresh tokens to minimize risk.
Absolutely. Kenko is designed to orchestrate endpoint calls and data flows with no code custom development. Use built in triggers, actions, and scheduled tasks to connect tag data and statistics to your workflows.
When a token expires, use the refresh token to obtain a new access token automatically. If refresh fails, re-authenticate via the GHL developer portal to reissue credentials.
The most common endpoints are the tags endpoint for tag retrieval and the statistics endpoints for engagement metrics. These are typically used to populate dashboards and automate reporting across Kenko workflows.
API documentation and changelogs are available in the GHL developer portal and the Kenko integration docs. These resources provide endpoint specifics, authentication steps, and example requests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
