Required scope: socialplanner/post.write. Authenticate using OAuth 2.0 or an API key, then grant Rosie access to post, edit, and delete social content through the Surveys API.
To authorize Rosie with Surveys API, create client credentials, configure the redirect URI, and grant the socialplanner/post.write scope so Rosie can manage posts on your behalf.
– POST /social-media-posting/:locationId/posts; Create a new post for a 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; Partially update a post Note: Additional endpoints exist in the API but are not shown here.
Trigger: When Rosie drafts a new post, create it in the Surveys API and return status back to Rosie.
Actions: POST to the create endpoint; map fields; update Rosie with postId and status; log activity.
locationId, postContent, media, scheduledTime
Trigger: Rosie requests an update to an existing post
Actions: PUT to update endpoint; propagate updated fields; refresh status in Rosie
PUT /social-media-posting/:locationId/posts/:id
id, locationId, updatedFields
Trigger: Rosie deletes a post
Actions: DELETE to the endpoint; mark as archived in Rosie; maintain audit trail
DELETE /social-media-posting/:locationId/posts/:id
id, locationId
Fast setup with no code: drag-and-drop field mappings and triggers to automate posting.
Real-time updates across platforms without custom development.
Centralized analytics and reporting for Rosie posts and audience engagement.
Key elements include API endpoints, triggers, actions, authentication methods, scope, and data fields used to connect Rosie with the Surveys API.
A specific URL in the Surveys API that performs a defined action, such as creating a post or updating a post.
The process of proving identity and granting permissions to access the Surveys API securely.
An event that starts a workflow, such as a new post draft in Rosie being ready to publish.
The set of permissions granted to Rosie to perform actions via the Surveys API (e.g., post.write).
Use audience analytics to schedule posts for Rosie automatically using the Surveys API.
Fetch trending hashtags via the API and append them to Rosie posts for better reach.
Create A/B variants of posts and compare performance using Rosie analytics.
Obtain API keys or OAuth credentials from Surveys API and configure Rosie.
Assign the socialplanner/post.write scope and test access.
Run test posts and monitor results in the Rosie dashboard.
To connect Rosie to the Surveys API, start by creating or selecting a Surveys API application and obtaining client credentials. Configure Rosie to use those credentials and request the socialplanner/post.write scope so Rosie can publish, edit, and delete posts on your behalf. After authorization, test a sample post to ensure the connection is working as expected.
Permissions are defined by the scope granted during OAuth or API key setup. Ensure Rosie has the socialplanner/post.write scope and any additional scopes your workflow requires. If you need read access, add the appropriate read scopes and verify in your app settings.
Available endpoints include create, update, delete, and patch for posts: POST, PUT, DELETE, PATCH on /social-media-posting/:locationId/posts and related paths. Some endpoints may be gated behind permissions; refer to the Surveys API docs for the full list.
Yes. Rosie can update or replace content for a post using the PUT or PATCH endpoints. Deleting a post is handled via DELETE, and archived status can be tracked within Rosie.
There is typically no hard limit imposed by Rosie, but API rate limits and location-based quotas may apply. Check your Surveys API plan for exact limits and consider staggering requests to stay within thresholds.
Testing is done by sending test posts from Rosie to the Surveys API in a sandbox environment or with a limited production location. Review API responses, logs, and Rosie analytics to verify success.
Analytics for Rosie posts are visible in the Rosie dashboard and can be linked to the Surveys API analytics. You can also export reports for engagement, reach, and post performance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers