Authenticate with the Surveys API using an API key issued in your GHL developer console and scoped to socialplanner/post.write. Use the Authorization header to pass your API key on each request.
Formester authenticates to the Surveys API by presenting the GHL API key and using the location based endpoints to post, update, or delete social content. Store credentials securely and rotate keys on a regular schedule.
Primary endpoints used: POST /social-media-posting/:locationId/posts, PUT /social-media-posting/:locationId/posts/:id, DELETE /social-media-posting/:locationId/posts/:id, PATCH /social-media-posting/:locationId/posts/:id. These cover creating, updating, deleting, and partially updating posts. Other endpoints exist in the API but are not required for this page.
Trigger: a new survey response is ready to be posted to social media.
Actions: POST to /social-media-posting/:locationId/posts to publish the update.
POST /social-media-posting/:locationId/posts
Required: locationId in the URL; body fields must include content, media URLs, and optional scheduling data.
Trigger: you need to modify a previously published post when survey data changes.
Actions: PUT to /social-media-posting/:locationId/posts/:id to update content.
PUT /social-media-posting/:locationId/posts/:id
Required: locationId, id, and a payload with updated content.
Trigger: end of campaign or removal is necessary.
Actions: DELETE /social-media-posting/:locationId/posts/:id
DELETE /social-media-posting/:locationId/posts/:id
Required: locationId and id.
Faster go-live with no coding required and a visual workflow to connect data sources.
Automate social posts from survey results to save time and reduce manual work.
Centralized API credentials simplify access control and rotation.
Key elements include endpoints, authentication and payload structures; processes cover connect, test, deploy, and monitor the integration between Formester and the Surveys API.
An API is a set of rules that lets software applications communicate and exchange data.
An endpoint is a specific URL in an API used to perform a defined action such as creating or updating a post.
OAuth 2.0 is an authorization framework that issues access tokens for secure API calls.
Location ID identifies a GHL location where posts are published and is used in API paths.
Automatically publish new survey results to connected social accounts using the Surveys API and Formester’s posting endpoint.
Use Formester to trigger follow-up posts or notifications when a survey cycle completes.
Plan posting times based on audience insights and publish at optimal moments.
In GHL, generate API credentials scoped to socialplanner/post.write and copy the API key to Formester.
Enter the API key into Formester’s integration settings and select the Surveys API as the target.
Run a test post with a mock locationId to verify authentication and endpoint paths.
The API name for this integration is Surveys API, used by GHL as the endpoint set for managing social posts from Formester. You will work with the Surveys API in the GHL developer console to create and manage credentials. In Formester, paste the API key and select the Surveys API as the target connection to begin posting.
Authentication is done with an API key issued in the GHL developer portal, scoped to socialplanner/post.write. Include the key in the Authorization header for each request. Formester also supports secure storage and rotation of credentials to maintain security.
The primary endpoints are POST /social-media-posting/:locationId/posts, PUT /social-media-posting/:locationId/posts/:id, DELETE /social-media-posting/:locationId/posts/:id, and PATCH /social-media-posting/:locationId/posts/:id. These allow you to create, update, delete, and partially update social posts from survey data.
Yes. You can automate posting by configuring triggers in Formester that call the Surveys API endpoints when survey results are ready or when certain conditions are met. This eliminates manual posting and speeds up publishing.
A Location ID identifies where posts will be published within GHL. It is required in the API path for location-specific posting and should be set up to reflect the target social location in your account.
To revoke access, remove the API credentials from Formester and revoke the API key in the GHL developer console. Rotating keys and updating configurations ensures ongoing security and control.
API credentials are generated in the GHL developer console. Copy the key, store it securely, and paste it into Formester’s integration settings. You can manage scopes and rotate keys from the same console.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
