Use your GHL API credentials to authorize requests to the Users API. Support token based auth and OAuth options depending on your setup.
TimeCamp uses an API key or OAuth flow to grant access to the Users API. Store keys securely and rotate regularly.
Available endpoints: 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 the API reference.
Trigger: a new tag is created in TimeCamp and should be added to the Users API.
Actions: call POST /social-media-posting/:locationId/tags/details to create or update tag details, and use GET /social-media-posting/:locationId/tags to retrieve current tags.
GET /social-media-posting/:locationId/tags
locationId, tagId, details
Trigger: request statistics via socialplanner/statistics.readonly.
Actions: POST /social-media-posting/statistics to push calculated metrics to the Users API.
POST /social-media-posting/statistics
startDate, endDate, metrics
Trigger: on-demand retrieval of tag data from GET /social-media-posting/:locationId/tags.
Actions: fetch tags via GET and push updates to TimeCamp dashboard; optionally post tag details.
GET /social-media-posting/:locationId/tags
locationId, tagId, name
Zero-code integration to sync tags and performance stats between TimeCamp and the Users API.
Automated workflows and alerts without writing code.
Centralized data with scalable endpoints for future growth.
Core elements and processes to understand when connecting TimeCamp with the Users API.
A specific URL and HTTP method used to access a resource in an API.
A method to verify identity and permissions before granting API access.
A URL endpoint that receives real-time data pushed by an API when events occur.
A cap on the number of API requests allowed in a given time window.
Set up a flow that copies new tags from TimeCamp to the Users API so dashboards stay current.
Create a daily summary of tag performance and post reach in the Users API.
Link events from TimeCamp to trigger custom actions in the Users API for seamless campaigns.
Obtain your API keys or set up OAuth from the TimeCamp and Users API dashboards.
Configure which TimeCamp events map to which Users API endpoints and data fields.
Run tests in a staging environment and monitor for errors before going live.
Yes, this is designed as a no-code integration. You can wire TimeCamp to the Users API using prebuilt endpoints and triggers. No coding is required for standard tag and statistics flows.
Endpoint availability is listed in the Endpoint List. Start with the tag endpoints and statistics endpoints. If you need more, consult the API reference for the full catalog of endpoints.
Authentication uses API keys or OAuth depending on your setup. Ensure your credentials are stored securely and rotated regularly. Test tokens to confirm access.
Yes, you can map and rename fields to fit your data model. Use the field mapping options in your integration settings and rely on the provided example paths.
Common issues include invalid credentials, misconfigured endpoints, and rate limits. Review your credentials, reauthorize if needed, and check endpoint paths.
Statistics updates depend on the endpoint: batch reads update on demand while some stats refresh on a schedule. Check your settings for frequency.
API documentation is available within the API reference linked in the Endpoint List. You can also access developer guides and example payloads there.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
