Use your GHL API key with the socialplanner/tag.readonly scope to authorize requests. Keep credentials secure and rotate keys regularly.
Grant Nearby Now access to the Users API by configuring OAuth or API tokens and selecting the required scopes. Store tokens securely.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Trigger: Location updates generate new tags for a given locationId.
Actions: Retrieve tags with GET /social-media-posting/:locationId/tags and store results in Nearby Now dashboards.
GET /social-media-posting/:locationId/tags
Key fields: locationId, tags, timestamp
Trigger: Daily or on-demand statistics generation.
Actions: Generate metrics via POST /social-media-posting/statistics and push to analytics dashboards.
POST /social-media-posting/statistics
Fields: metrics, timestamp, locationId
Trigger: User requests detailed tag information for a location.
Actions: Call POST /social-media-posting/:locationId/tags/details to fetch nested tag data.
POST /social-media-posting/:locationId/tags/details
Fields: locationId, tagDetails, detailsTimestamp
Faster setup with ready-to-call endpoints—no heavy coding required.
Access real-time data for location-based campaigns and optimization.
Automations and triggers keep data flowing without writing code.
A concise glossary of terms used in the Nearby Now and Users API integration to help you design faster.
Definition: A published interface that lets software systems communicate.
Definition: A specific URL that performs a function within an API.
Definition: The process of verifying identity and authorizing access.
Definition: A label used to categorize data for filtering and reporting.
Surface live location tags from the Users API and push them into Nearby Now campaigns for timely engagement.
Feed dashboards with statistics data to visualize trends across locations.
Fetch details for a specific tag when a user requests deeper context.
Obtain API keys and set the proper scope for tag and statistics access.
Select the endpoints you need and test connectivity with sample calls.
Create automations to pull tags and statistics and monitor for issues.
Authenticate via API key and OAuth as appropriate. Ensure the token has the socialplanner/tag.readonly scope. Test the connection with a quick GET call to tags and verify the response. Store keys securely and rotate them regularly. Consider using environment variables or a secrets manager for added security.
Start with the endpoints that match your needs: tags retrieval, tag details, and statistics. Use GET for fetching tags, POST for details and statistics when you need a deeper view. Validate each call in a staging environment before going live.
No-code options exist via built-in connectors and workflows. If you need custom logic, lightweight scripting or webhooks can extend capabilities without a full codebase. Always test automations thoroughly.
Required scopes include socialplanner/tag.readonly for reading tags and statistics endpoints for metrics. Keep tokens secure and limit access to trusted apps.
Use sandbox/test endpoints when available. Validate responses, check status codes, and verify data accuracy. Start with small location sets and scale gradually.
Yes, you can poll multiple locationIds. Use parameters like locationId to iterate and aggregate data, or set up parallel requests with appropriate rate limits.
Treat API keys like passwords: rotate keys, restrict access, and use IP whitelisting where possible. Enable secure storage and monitor for unauthorized usage.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
