Authenticate requests to the Blogs API using OAuth 2.0 with the scope emails/builder.readonly, and securely store credentials in Rankr.
Authorize Rankr to access your Blogs API data by completing the OAuth flow and granting the necessary scopes.
Endpoints include: GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; emails/schedule.readonly; GET emails/schedule; blogs/post.write; POST /blogs/posts; blogs/post-update.write; PUT /blogs/posts/:postId; blogs/check-slug.readonly; GET /blogs/posts/url-slug-exists; blogs/category.readonly; GET /blogs/categories; blogs/author.readonly; GET /blogs/authors.
Trigger: when a new draft is saved in Rankr push a post to Blogs via POST /blogs/posts
Actions: create posts set slug attach author and category return postId
Key methods POST /blogs/posts PUT /blogs/posts/:postId
Required fields title content slug author category status
Trigger: new blog post created in Rankr triggers template generation or update in Blogs API
Actions: create update emails builder templates embed post content
Methods: GET emails/builder POST emails/builder POST /emails/builder/data
Key fields templateId locationId subject body postId
Trigger: when a post is approved in Rankr publish via PUT /blogs/posts/:postId
Actions: publish update status sync slug
Methods: POST /blogs/posts PUT /blogs/posts/:postId
Key fields postId title content slug status
Automate repetitive tasks without writing code
Keep content consistent across channels and apps
Speed up publishing cycles and improve accuracy
This glossary defines critical terms like endpoints authentication mapping and data fields used in the Blogs API integration with Rankr
A specific URL path and HTTP method used to perform an action in an API
An authorization framework that lets apps obtain limited access to a user’s data without exposing credentials
A secret token used to authenticate API requests
A URL friendly identifier derived from a post title used for SEO
Pulls top posts from Rankr and distributes a summary via email templates in Blogs API
Generate draft posts with SEO friendly slugs and metadata ready for publishing
Automatically mirror new posts to social networks after approval
In the Blogs API dashboard generate an API key or set up OAuth credentials for Rankr
Run the OAuth flow grant the scope and run test requests to verify endpoints like GET /blogs/authors
Define field mappings between Rankr posts and Blogs API endpoints to enable seamless automation
The Blogs API provides programmatic access to your blog content templates and scheduling. With Rankr you can automate how posts are created edited and published. This eliminates repetitive manual steps and speeds up publishing. The combination of APIs enables consistent content across channels.
Authentication uses OAuth 2.0 with the required scopes and or API keys. Store credentials securely and rotate keys regularly. If you use Rankr authorize the app and test endpoints to confirm access rights.
Available endpoints include emails builder schedule and blog endpoints such as GET emails/builder POST /blogs/posts PUT /blogs/posts/:postId GET /blogs/posts/url-slug-exists and more. Refer to the endpoint list for a complete map of actions.
Yes you can update existing posts using PUT /blogs/posts/:postId. Creating new posts uses POST /blogs/posts. Ensure you pass the correct postId and pass required fields. Maintain idempotency where possible.
Call GET /blogs/posts/url-slug-exists to check slug availability. The response indicates if the slug is already in use. If taken modify the slug or allow the system to propose an alternative.
Email templates are built via the emails builder endpoints. Use POST /emails/builder and POST /emails/builder/data to populate content and subject lines. Include post reference when needed.
Best practices include careful field mapping and thorough testing in a sandbox, monitoring error logs, and keeping content in sync across Rankr and Blogs API. Document mappings and maintain versioned endpoints to avoid breaking changes.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
