To connect, obtain your Surveys API credentials from the GHL developer console and configure them in the Tokko Broker app connector. Ensure the required scope is granted (socialplanner/post.write) to enable posting.
Within Tokko Broker, enter the Surveys API credentials and select the appropriate authentication method (API key or OAuth 2.0 as supported). Verify the connection with a test post before going live.
Core endpoints included in this integration: 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
When a new listing goes live in Tokko Broker, trigger a drafted post in Surveys API for review and scheduling.
Generate post content, attach listing media, set a publish date, and push to the /social-media-posting/:locationId/posts endpoint.
POST to /social-media-posting/:locationId/posts
locationId, content body, media links, scheduledTime
If post content or timing needs adjustment after initial creation, update the existing post in Surveys API.
Modify content, timing, or status; ensure validations pass before rescheduling.
PUT /social-media-posting/:locationId/posts/:id
locationId, id, updatedContent, updatedScheduledTime
If a post should be removed before publishing, delete it from Surveys API.
Send a DELETE request to remove the post from the location.
DELETE /social-media-posting/:locationId/posts/:id
locationId, id, authorization
Speed: connect and automate postings within minutes without writing code.
Automation: synchronize listings, posts, and schedules across platforms automatically.
Reliability: built-in retries and error handling keep posts consistent.
This glossary defines endpoints, triggers, actions, and fields used to connect Tokko Broker with the Surveys API.
A specific URL path exposed by the Surveys API used to perform an action (e.g., posting content).
An event that starts an automation in Tokko Broker when a condition is met (e.g., new listing published).
An operation such as POST, PUT, PATCH, or DELETE that changes data in Surveys API or Tokko Broker.
A unique identifier for a posting location within Tokko Broker where posts are published.
When a new listing is added, automatically generate and queue a series of posts across platforms using the Surveys API.
Route posts to different audience segments (buyers, sellers, investors) by mapping fields between Tokko Broker and Surveys API.
Post status updates and performance metrics to a dashboard via the API for real-time monitoring.
Obtain credentials from GHL and configure them in Tokko Broker; grant the socialplanner/post.write scope.
Map Tokko Broker fields to Surveys API payloads for posts and ensure endpoints are enabled in your app settings.
Run test posts, verify responses, and monitor logs before going live.
No-code integration is designed to be approachable for marketers and admins. You can connect Tokko Broker to Surveys API using guided setup in the app connector, then configure fields and endpoints without writing code. If you have complex needs, you can still customize payload mappings through the connector’s UI. Two practical tips: start with a simple test post to validate authentication and endpoint access, and use the built-in logs to verify payloads and responses.
The essential endpoints for posting are the create, update, delete, and modify actions on posts. Specifically: POST /social-media-posting/:locationId/posts to create a post, PUT /social-media-posting/:locationId/posts/:id to update, PATCH /social-media-posting/:locationId/posts/:id for minor changes, and DELETE /social-media-posting/:locationId/posts/:id to remove a post. You’ll map Tokko Broker listing fields to the API payload for content and scheduling.
Authenticate by using your Surveys API credentials from GHL and granting the required scope (socialplanner/post.write). In Tokko Broker, select the Surveys API as the connected app and input the credentials. Run a quick test to confirm the connection and ensure valid responses from the API.
Yes. You can schedule posts by including a scheduled time in the payload when creating a post with POST. You can also update the schedule later with PUT or PATCH. Ensure your timezone and scheduling format are consistent to avoid mismatches.
Common errors include authentication failures, invalid locationId or post ID, and payload validation issues. Check your API credentials, confirm the locationId exists, and verify that required fields such as content and scheduledTime are present and correctly formatted.
Mapping fields involves aligning Tokko Broker listing data (title, description, images, location) with the Surveys API post payload (content, media, scheduling). Use the connector’s field-mapping UI to define sources and destinations, and test with sample listings to ensure fidelity.
API credentials are found in the GHL developer console for the Surveys API. Create an app, generate an API key or OAuth credentials, and configure them in Tokko Broker’s app connector. Store credentials securely and rotate them periodically.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
