Authenticate using OAuth 2.0 to grant 2Chat the socialplanner/post.write permission. Use short‑lived tokens and refresh as needed.
In 2Chat, provide the API key or OAuth token obtained from Surveys API to establish a secure connection and start posting on your behalf.
– POST /social-media-posting/:locationId/posts — Create a new post for a given location. – PUT /social-media-posting/:locationId/posts/:id — Update an existing post. – DELETE /social-media-posting/:locationId/posts/:id — Delete a post. – PATCH /social-media-posting/:locationId/posts/:id — Partial update of a post.
Trigger: a new post is created in 2Chat and is pushed to Surveys API for logging and reporting.
Actions: create post in Surveys API, return postId, set initial status, and sync back to 2Chat.
POST /social-media-posting/:locationId/posts
locationId, id, content, media, scheduledTime, status
Trigger: updates in 2Chat post reflect in Surveys API to keep data aligned.
Actions: update post (PUT/PATCH), propagate changes, maintain audit trail.
PUT /social-media-posting/:locationId/posts/:id
locationId, id, content, status
Trigger: deleting a post in 2Chat triggers deletion in Surveys API to avoid orphaned data.
Actions: delete post in Surveys API, option to archive records for audit.
DELETE /social-media-posting/:locationId/posts/:id
locationId, id
Faster campaign setup by reusing survey data to auto-generate social content.
A unified workflow across Surveys API and 2Chat for analytics and reporting.
Secure token-based authentication with scoped access and revocation controls.
Key elements include API endpoints, authentication, data mapping, triggers, responses, and error handling to ensure reliable data flows between Surveys API and 2Chat.
A defined URL and HTTP method used to perform a specific action on a service.
The process of verifying identity and permissions before granting access to resources.
A social media update prepared for publishing.
Open Authorization protocol used to securely grant access without sharing credentials.
Automatically generate social posts from survey responses to keep content fresh and relevant.
Create multiple post variants from a single survey to test engagement.
Monitor how posts perform and adjust future content with live data.
Obtain a client ID/secret or API key from Surveys API and configure in 2Chat.
Select endpoints and define field mappings for posts, statuses, and IDs.
Run tests to ensure data flows correctly and deploy to production.
Authentication uses OAuth 2.0; obtain tokens from Surveys API and configure in 2Chat to establish a secure connection. Tokens should be stored securely and refreshed as needed; the post.write scope governs what 2Chat can do.
For basic posting, you need the POST endpoint to create posts. You may also use PUT or PATCH for updates and DELETE to remove posts; map fields like locationId, id, content, and scheduling details.
Yes, you can update posts via PUT or PATCH. Deletion uses the DELETE endpoint; include locationId and id to identify the post.
Common mapped fields include locationId, id, content, media, scheduledTime, and status. Proper mapping ensures data parity across both systems.
Use TLS for transport, store tokens securely, and apply least-privilege access. Rotate credentials regularly and monitor access.
Rate limits depend on the API tier; monitor response headers and implement exponential backoff to handle bursts gracefully.
Developer docs are available on the Surveys API portal and the 2Chat integration guide. Expect payload examples and endpoint references.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
