Authenticate to Surveys API using API keys or OAuth. Ensure the requested scope includes socialplanner/post.write for posting updates.
Grant Acadimiat the necessary permissions to access Surveys API resources. Use least-privilege access, rotate credentials regularly, and store tokens securely.
POST /social-media-posting/:locationId/posts — Create a new social post; PUT /social-media-posting/:locationId/posts/:id — Update a scheduled post; DELETE /social-media-posting/:locationId/posts/:id — Remove a post; PATCH /social-media-posting/:locationId/posts/:id — Partial update to a post. Additional endpoints available as needed for advanced workflows.
Trigger when a new survey response is recorded in Acadimiat to automatically create a social post.
Actions: format message, optionally attach media, and publish via POST /social-media-posting/:locationId/posts.
POST /social-media-posting/:locationId/posts
locationId, content, mediaUrl (optional), author, scheduledTime
Trigger when a post needs content edits or timing adjustments before publishing.
Actions: modify content or media, then send PUT to update the post.
PUT /social-media-posting/:locationId/posts/:id
locationId, id, content, mediaUrl, scheduleTime
Trigger when a post is no longer required or violates policy.
Actions: delete via DELETE endpoint to remove the post.
DELETE /social-media-posting/:locationId/posts/:id
locationId, id
Automate workflow without writing code, using visual triggers and pre-built actions.
Fast setup with drag-and-drop configurations and ready-to-use templates.
Scalable data flow from survey responses to social posts across channels.
Key elements include API authentication, endpoints, data mapping, and workflow triggers that connect Acadimiat to Surveys API.
The method used to prove identity and grant access to the Surveys API.
A specific URL path that performs a defined operation in the API.
A callback to notify Acadimiat of events in Surveys API.
Industry-standard protocol for granting access without sharing passwords.
Automatically generate and publish social posts as soon as a survey response is submitted, capturing sentiment and key metrics.
Map survey fields to post content to tell a data-driven story across platforms with consistent branding.
Experiment with different post formats and timings using no-code automations to optimize engagement.
Collect your API key or set up OAuth credentials for Surveys API and grant Acadimiat the required permissions.
Define how survey fields route into Acadimiat’s data model and posts, ensuring consistent content structure.
Run tests, verify triggers, validate authentication, and deploy the workflow to production.
API authentication can use API keys or OAuth 2.0 tokens. Store credentials securely, rotate keys regularly, and apply the least-privilege principle to limit access to only what is required for posting. For production, prefer OAuth for long-term access and monitor token usage for anomalies.
The primary endpoints for creating and managing social posts are provided in the Endpoint List. Use POST to create, PUT to update, PATCH for partial updates, and DELETE to remove posts. Additional endpoints may be available for advanced automation and analytics as your workflow expands.
Field mapping ensures survey data aligns with Acadimiat’s post structure. You can map questions, responses, and metadata to content blocks, media fields, and scheduling attributes. This enables consistent, data-driven posts across channels.
No-code tooling within Acadimiat and Surveys API lets you configure triggers, mappings, and actions without writing code. You can assemble the workflow with visual builders, templates, and test runs before going live.
Respect data privacy by limiting scopes, using secure storage for credentials, and logging access. Ensure users have consent for data use and post publication, and review permissions regularly.
Testing involves validating authentication, confirming endpoint responses, and simulating survey triggers. Use test locations, verify content formatting, and confirm posts publish as expected before production.
Endpoint details and examples are available in your API docs and the Endpoint List above. Review method paths, required parameters, and example payloads to accelerate setup and troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
