Authenticate requests with an API key or OAuth token from your GHL developer portal, and include it in the Authorization header for each call.
Dashly uses OAuth 2.0 for user authorization and supports API key-based access for secure server-to-server calls.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics. Additional endpoints are documented in your GHL docs.
Trigger: when a tag is added or updated in Dashly, push changes to the Users API to keep data in sync.
Actions: create or update tags in the Users API, fetch the latest tag list, and reflect updates in Dashly dashboards.
GET /social-media-posting/:locationId/tags
locationId, tags
Trigger: daily (or on-demand) statistics pulled from the Users API into Dashly.
Actions: fetch /social-media-posting/statistics and update Dashly dashboards.
POST /social-media-posting/statistics
locationId, date_range
Trigger: new post activity or tag changes in the Users API triggers enrichment in Dashly.
Actions: pull activity/feed data, attach to Dashly narratives, and alert relevant teams.
GET /social-media-posting/:locationId/tags/details
locationId, tag_id
Automations eliminate manual data entry by syncing tags and statistics automatically.
Visual workflows let teams connect Dashly and GHL without writing code.
Faster onboarding and scalable data sharing between platforms.
This glossary clarifies endpoint names, authentication methods, and common data flows used in the Dashly–Users API integration.
A specific URL in your API that performs a defined action, such as retrieving or updating data.
An authorization framework that lets Dashly access the Users API securely without sharing user credentials.
A secret token used to authorize requests to the Users API.
A callback mechanism where the API sends real-time data to Dashly when events occur.
Set up a background task to automatically synchronize tags between Dashly and the Users API to keep data fresh.
Embed live statistics from the Users API into Dashly dashboards for quick insights.
Enable one-click exports to CSV or BI tools to share reports.
In GHL, generate an API key with appropriate scopes (for example, tag.readonly); copy the key to Dashly.
In Dashly, enter credentials and authorize the connection to the GHL API.
Run a quick test call to fetch tags and statistics and verify the data flow.
Authentication should be done via an API key or OAuth token issued in the GHL developer portal. Include the Authorization header in every request. For Dashly, ensure the token has the required scope (e.g., tag.readonly) and rotate secrets regularly.
Essential endpoints to start are GET /social-media-posting/:locationId/tags and POST /social-media-posting/:locationId/tags/details for tagging, plus socialplanner/statistics.readonly and POST /social-media-posting/statistics for metrics. Additional endpoints are available in your GHL docs.
To test the connection, run sample calls against a test locationId (fetch tags and statistics) and verify responses. Check that authentication succeeds and data maps correctly into Dashly dashboards.
No-code flows via Dashly are supported, but be mindful of API rate limits. If you encounter limits, implement backoff and staggered syncs to maintain stability.
Yes. Use the statistics endpoints to fetch metrics and feed them into Dashly dashboards, or export data to CSV/BI tools as needed.
Store API keys securely, use least privilege scopes, and rotate credentials regularly. Enable webhook verification and monitor activity logs for unusual access.
Documentation is available in the GHL developer portal. If something is missing, contact support for access to extended endpoint references and samples.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
