To securely connect, generate an API key with the socialplanner/post.write scope and exchange tokens between Phone-com and Surveys API.
Phone-com authenticates to Surveys API using the provided API key or OAuth token; keep credentials secure and rotate periodically.
Endpoint 1: POST /social-media-posting/:locationId/posts — Create a new post for a given location. Endpoint 2: PUT /social-media-posting/:locationId/posts/:id — Update an existing post. Endpoint 3: DELETE /social-media-posting/:locationId/posts/:id — Delete a post. Endpoint 4: PATCH /social-media-posting/:locationId/posts/:id — Partially update a post. Endpoints 5-17: Additional capabilities such as bulk creation, status checks, scheduling, and bulk updates will be available as you expand integration.
Trigger: a new draft is saved in Phone-com; Surveys API creates a post.
Actions: POST to /social-media-posting/:locationId/posts; return the post ID and status.
Method Path: POST /social-media-posting/:locationId/posts
Key fields: locationId, content, mediaUrl, scheduledTime
Trigger: post draft updated in Phone-com
Actions: PUT /social-media-posting/:locationId/posts/:id
Method Path: PUT /social-media-posting/:locationId/posts/:id
Key fields: locationId, id, content
Trigger: post is no longer needed
Actions: DELETE /social-media-posting/:locationId/posts/:id
Method Path: DELETE /social-media-posting/:locationId/posts/:id
Key fields: locationId, id
No-code automation reduces manual posting time and accelerates campaign production.
Centralizes content across locations with a single integration point.
Improved visibility with built-in analytics and scheduling.
Key elements: endpoints, HTTP methods, triggers, actions, and required fields; processes: authentication, authorization, and error handling.
An application programming interface that allows applications to communicate and access features from Surveys API.
A specific URL and HTTP method combination that performs an action in Surveys API, e.g., POST /social-media-posting/:locationId/posts.
The process of verifying identity and permissions to access Surveys API.
A standard authorization framework used to grant access to resources without sharing user credentials.
Automatically convert new Phone-com drafts into ready-to-publish posts in Surveys API.
Queue multiple posts for different locations with a single workflow.
Use Surveys API data to populate reporting dashboards inside Phone-com.
Obtain API key with the required scope and configure in Phone-com.
Map Phone-com fields to Surveys API endpoints and test.
Run tests, verify responses, and enable live posting.
Surveys API supports API key authentication and OAuth tokens. For Phone-com, use a secure API key with scope socialplanner/post.write. Store credentials securely and rotate them regularly. You can also revoke access if needed. Ensure redirect URIs are whitelisted and monitor token expiry to keep the integration seamless.
Basic posting requires locationId and content. Optionally include mediaUrl and scheduledTime. Use POST /social-media-posting/:locationId/posts to create, then use PUT or PATCH for updates. Test with a sandbox location first and log response IDs for troubleshooting.
To test the integration, use a staging environment and mock responses. Validate HTTP status codes, response bodies, and that posts appear in the target social networks. Use sample locationId values and track IDs for end-to-end verification.
Yes. Scheduling is supported by providing scheduledTime in the post payload. Ensure timezone awareness and verify that scheduled posts publish at the correct time in your target locations.
Required fields typically include locationId and content. Additional fields like mediaUrl and scheduledTime are optional but recommended for richer posts. For updates, id is required alongside locationId.
API keys are created in your Surveys API account. They should be stored securely in Phone-com’s settings and rotated regularly. Ensure the key has the correct scope (socialplanner/post.write) for posting operations.
Common errors include 401/403 for authentication or authorization issues, 404 for missing resources, and 429 for rate limits. Check your scopes, verify locationId and post IDs, and review your request payload format and required fields.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
