Authenticate with OAuth 2.0 using your GHL application credentials to securely access the Users API endpoints for StreamYard.
StreamYard uses standard API keys or OAuth flows configured during app setup to securely authenticate requests to the Users API.
– GET /social-media-posting/:locationId/tags – POST /social-media-posting/:locationId/tags/details – socialplanner/statistics.readonly – POST /social-media-posting/statistics
Triggers when a location is selected for posting to pull tag data before publishing.
Actions: fetch tags (GET) and fetch tag details (POST).
GET /social-media-posting/:locationId/tags
Location ID is required; response returns tag IDs and names.
Triggered when a tag needs additional metadata before posting.
Actions: post details to /social-media-posting/:locationId/tags/details.
POST /social-media-posting/:locationId/tags/details
Requires locationId and tagId; payload includes detail fields.
Triggered after publish or on a schedule to update metrics.
Actions: POST /social-media-posting/statistics; optionally GET socialplanner/statistics.readonly to fetch insights.
POST /social-media-posting/statistics
Location ID and metrics payload; includes impressions, clicks, engagements.
No-code automation: Set up workflows without custom code.
Centralized data sync across StreamYard and your analytics in one place.
Faster publishing with live tag data and statistics to optimize social campaigns.
Key elements you’ll encounter include endpoints, authentication, payload schemas, and data mapping between GHL and StreamYard.
API: A set of endpoints and methods that let apps talk to each other to exchange data securely.
Endpoint: A specific URL and HTTP method used to perform an action.
Authentication: Verifying identity to grant access to protected resources (e.g., OAuth tokens).
Webhook: A server-to-server callback that notifies you of events in real time.
Automatically pull tags before going live to tailor your stream topics and overlays.
Post-session analytics trigger tags to highlight key moments in future streams.
Schedule content based on engagement metrics pulled from the Users API.
Obtain your GHL client credentials and authorize the StreamYard app to access the Users API.
Connect the required endpoints for tags and statistics to your StreamYard workflows.
Run tests, validate data flow, and set up automated posting schedules.
The integration connects StreamYard with the Users API to automate tag management and statistics reporting during live streams. You can pull location tags to inform stream topics and overlays, then push tag details back to enrich content. This creates cohesive, data-driven broadcasts without manual data entry. Use cases include pre show tag selection, live tagging, and post show analytics that fuel future streams.
No heavy coding is required. This guide uses RESTful endpoints and a standard OAuth flow to authorize the app. Most setups involve configuring a few parameters in your StreamYard connection and mapping fields between responses and your posting workflow. If you already have a no-code automation stack, you can plug in the endpoints directly without writing server code.
For basic publishing, the essential endpoints are the GET tags and POST tags/details for tag enrichment. The statistics endpoints help you measure performance. If you only need to publish content now, you can start with tags endpoints and later add statistics as needed.
Always protect your client IDs, secrets, and tokens. Use short-lived tokens, store credentials securely, and rotate keys periodically. Implement least privilege access and use OAuth scopes to limit what the integration can do. Consider enabling IP allowlisting and auditing any access to the GHL account.
Yes. The statistics endpoint set lets you pull impressions, clicks, and engagement metrics. You can use these in dashboards, reports, and to optimize your posting schedule. Regularly review metrics to adjust content strategy and posting cadence.
Tag data typically includes tag IDs, names, and any metadata you attach during the details step. You can map these fields to your StreamYard overlays or publish workflows to ensure consistent labeling. If more fields are needed, extend the payload with additional metadata.
Endpoint details are provided in the official API reference for the GHL Users API. In this guide, endpoints are summarized with their methods and example paths. For full schema and field-level descriptions, consult your API documentation or developer portal.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
