To connect, create API credentials in Surveys API and grant Moskit access with the social planner scope. Use the token or OAuth method supported by Surveys API.
In Moskit, store credentials securely and configure redirect URIs if using OAuth. Then connect Moskit to Surveys API with those credentials.
Endpoint1: POST /social-media-posting/:locationId/posts — create a new post. Endpoint2: PUT /social-media-posting/:locationId/posts/:id — update an existing post. Endpoint3: DELETE /social-media-posting/:locationId/posts/:id — delete a post. Endpoint4: PATCH /social-media-posting/:locationId/posts/:id — partially update a post.
Trigger: A new Moskit post is created or scheduled
Actions: Create a post in Surveys API at locationId with content and media, then publish or schedule.
POST /social-media-posting/:locationId/posts
locationId, content, media, scheduling, status
Trigger: Moskit post edits are detected
Actions: Update the corresponding Surveys API post via PUT with new content and media
PUT /social-media-posting/:locationId/posts/:id
locationId, id, updated_content, updated_media
Trigger: Moskit post is deleted or archived
Actions: Delete the related Surveys API post via DELETE
DELETE /social-media-posting/:locationId/posts/:id
locationId, id
Automate manual posting workflows without writing code
Consolidate content, schedules, and results in one workflow
Scale publishing across channels quickly with consistent messaging
Key elements include endpoints, triggers, actions, authentication, data mapping, and error handling to keep workflows smooth.
API stands for Application Programming Interface, a set of rules that lets apps talk and share data.
An API URL and method that perform a specific action, such as creating or updating a post.
Process to verify identity and grant access, via OAuth tokens or API keys.
A callback endpoint that receives real-time data when events occur.
Automatically pull Moskit drafts into a shared calendar and schedule posts via Surveys API.
Coordinate campaigns across platforms using a single Moskit trigger and the Surveys API.
Aggregate engagement metrics from Surveys API to Moskit dashboards for insights.
Create API credentials in Surveys API and note client ID and secret or access token.
Map fields between Moskit and Surveys API, including locationId, content, media, and scheduling.
Test in staging, verify data flows, and push to production with monitoring.
Prereqs include a Moskit account and a Surveys API subscription with the social planner scope. You will need admin rights to generate API credentials and set up authorized redirects if using OAuth. Ensure your Moskit workspace can reach the Surveys API endpoints over a secure connection. After setup, test connectivity with a sample post.
For basic posting, endpoints 1 and possibly 2 are sufficient. Create a post with POST, then use PUT to update if edits are needed. You can start with endpoint 4 for partial updates if supported. Always validate responses and handle errors gracefully.
Authentication is handled via tokens or OAuth as supported by Surveys API. Store tokens securely, rotate regularly, and use scoped access. If you see auth errors, reissue credentials and verify redirect URIs.
Yes. You can schedule posts by including a scheduling field in the payload or by using a queue in Moskit. The Surveys API accepts scheduling parameters for future publishing.
Endpoint errors typically return status codes and messages. Check error details, retry with backoff, and confirm that your locationId and post payload match the API schema. Implement robust error handling in the Moskit workflow.
Middleware like Zapier is not required but can simplify connections. If you prefer code-free automation, Moskit to Surveys API can be wired directly via webhooks or built-in actions.
Credentials and logs are found in the Surveys API dashboard and Moskit integration settings. Enable audit logs and monitor for failed requests. Use the API explorer in Surveys API for testing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
