To securely access the Blogs API from Rankr, configure your API credentials and set the required scope (emails/builder.readonly is the example scope). Store credentials securely and rotate keys as needed.
Rankr uses token based access to connect to external APIs. Ensure the Blogs API credentials are granted and tested in a safe environment.
Email 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. Blog endpoints include POST /blogs/posts; GET /blogs/posts/url-slug-exists; PUT /blogs/posts/:postId; GET /blogs/categories; GET /blogs/authors; GET /blogs/categories. Additional endpoints include GET /blogs/categories and GET /blogs/authors for lists and mapping.
Trigger: A new post is created or updated in Rankr.
Actions: POST /blogs/posts to create the post and POST /blogs/posts data to supply content; manage slug as needed.
POST /blogs/posts
title, content, slug, author, categories
Trigger: Rankr content changes in an article.
Actions: PUT /blogs/posts/:postId to update; GET /blogs/posts/url-slug-exists to sanitize slug.
PUT /blogs/posts/:postId
postId, title, content, slug
Trigger: Rankr adds a new category or author.
Actions: GET /blogs/categories to fetch categories and GET /blogs/authors to fetch authors; map to Rankr fields.
GET /blogs/categories and GET /blogs/authors
categoryId, authorId
Automate blog publishing without writing code using Rankr visual workflows.
Centralized content management lets you update posts and metadata from one place.
Maintain consistent SEO friendly slugs and post fields across platforms.
Key terms explained: endpoints, triggers, actions, fields, and slug checks, mapped to Rankr workflows.
A specific URL path and HTTP method used to perform an API operation.
An event in Rankr that starts an automation or data sync.
An operation executed against the API, such as create or update.
A URL friendly string derived from the post title used to identify posts.
Automatically generate outlines in Rankr and publish as blog posts via POST /blogs/posts.
Sync a calendar in Rankr to trigger scheduled posts via the Blogs API.
Push Rankr edits to existing posts with PUT /blogs/posts/:postId.
Obtain API credentials for the Blogs API and authorize Rankr to access posts, categories, and authors.
Link Rankr fields to Blog post fields: title → title, body → content, slug, categories.
Set triggers for new or updated content and map actions to create or update posts.
Core blog endpoints include POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update, GET /blogs/posts/url-slug-exists to check slug availability, GET /blogs/categories to list categories, and GET /blogs/authors to list authors. You can combine these to build full content workflows. The blog endpoints are designed to be used with Rankr to automate publishing, updating, and classification.
Authentication requires valid API credentials with the correct scopes. Use the provided scope (emails/builder.readonly) for read access and request appropriate write scopes for posting or updating content. Always test in a staging environment and rotate keys regularly.
Yes. Email templates are managed through the Emails API endpoints such as POST emails/builder to create a template and DELETE emails/builder/:locationId/:templateId to remove one. You can keep email templates separate from blogs but still trigger blog actions from Rankr as needed.
Scheduling can be driven by Rankr via triggers and the Blogs API publish flow. You can use Rankr automation to set a publish date and call POST /blogs/posts when the time arrives, or use calendar-based triggers to push content to the API.
Slug conflicts are prevented by checking slug existence with GET /blogs/posts/url-slug-exists before creating. If a slug already exists, modify it by appending a unique suffix or a timestamp.
Fetch categories with GET /blogs/categories and authors with GET /blogs/authors. Map the IDs to Rankr fields for consistent routing and display in your UI.
API docs and examples for the Blogs API and Rankr integration are available in the developer portal. Review endpoint references, payload formats, and sample workflows to implement your setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
