Obtain an access token, configure your API key or OAuth credentials, and grant Rankr permission to access the Surveys API posting endpoints.
During setup, authorize Rankr to use your Surveys API credentials and store tokens securely with automatic refresh.
POST /social-media-posting/:locationId/posts; PUT /social-media-posting/:locationId/posts/:id; DELETE /social-media-posting/:locationId/posts/:id; PATCH /social-media-posting/:locationId/posts/:id
Trigger: when a new post draft is approved in Rankr, automatically push to Surveys API to publish.
Actions: POST to create a post, then optionally update with PUT or PATCH as needed using locationId and post content.
POST /social-media-posting/:locationId/posts
Required fields include locationId, content, scheduledTime (optional), and visibility
Trigger: edits in Rankr trigger updates in Surveys API to keep posts accurate.
Actions: PUT or PATCH to modify post content and metadata on the fly.
PUT /social-media-posting/:locationId/posts/:id
Key fields: locationId, id, content, status
Trigger: small changes saved without replacing the entire post.
PATCH /social-media-posting/:locationId/posts/:id
Key fields: locationId, id, partialContent, updatedAt
Automate routine posting without writing code
Reduce manual errors and accelerate campaigns
Centralized control through the Rankr dashboard
This glossary defines core terms like API Endpoint, Authentication, Location ID, and Triggers that power the Surveys API integration with Rankr.
A defined URL and HTTP method used to perform an action in an API.
A specific identifier that points to a social channel or account location in Surveys API.
The process of proving identity and obtaining an access token to call the API securely.
A URL that receives events from Surveys API to notify Rankr of changes.
Automatically generate and schedule social posts when Rankr campaigns meet engagement thresholds.
Leverage Surveys API insights to adjust posting times for peak engagement.
Publish from Rankr to multiple platforms through a single Surveys API workflow.
In Surveys API, create a new app credential and authorize Rankr to use it.
Assign the social posting endpoints and set the scope to socialplanner/post.write.
Run test posts and verify responses to ensure the integration works as expected.
Authentication is done by generating an access token or using an API key from Surveys API and then attaching it to requests from Rankr. Store credentials securely and rotate them regularly. If using OAuth, ensure the redirect URI is registered for Rankr. Always use HTTPS when transmitting tokens. Monitor token expiry and refresh tokens automatically where supported.
For posting, you primarily use the POST endpoint to create new posts. You may also use PUT to update an existing post or PATCH for partial updates. Ensure the locationId correlates to the correct social channel and include the post content, scheduling, and visibility. For updates, provide the post id to modify the correct resource.
Yes. You can update posts after publishing by using PUT or PATCH with the post id. This allows you to fix content, timing, or visibility without recreating the post. Always verify the response to confirm the update took effect.
There is a no code flow via Rankr where you connect using API credentials and configure endpoints without writing code. Rankr provides a guided setup and visual workflow to map fields to the Surveys API endpoints.
You typically need read and write permissions for social posting and the ability to manage posts. The exact scopes should include socialplanner/post.write and any related read permissions required for your workflow.
Test the integration by running a sandbox post through Rankr to the Surveys API and checking the response status and resulting post state. Validate success criteria such as post creation, updates, and scheduling correctly reflect in your social channels.
API rate limits depend on your Surveys API plan. Check the dashboard or provider docs for limits, throttling rules, and best practices to avoid hitting limits. If you exceed limits, implement backoff retry logic and queueing in Rankr.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
