Requests to the Blogs API are authenticated with a combination of API keys and OAuth tokens. Secure credentials, request appropriate scopes, and test connections in a staging environment before going live.
In Rankr, create a service integration for the Blogs API, grant only the required permissions, and rotate credentials on a regular schedule to maintain security.
GET emails/builder — retrieve email templates (example structure for integration); POST emails/builder — create a new email template; POST /emails/builder/data — supply email content; DELETE /emails/builder/:locationId/:templateId — remove templates; emails/schedule.readonly — view email schedules; GET emails/schedule — list email schedules; POST /blogs/posts — create a blog post; PUT /blogs/posts/:postId — update a post; GET /blogs/posts/url-slug-exists — check slug availability; GET /blogs/categories — list categories; GET /blogs/authors — list authors; GET /blogs/posts/url-slug-exists — slug validation; GET /blogs/categories — fetch categories; GET /blogs/authors — fetch authors.
Trigger when a new draft is created in Rankr to push to the Blogs API and create a new post.
Actions include creating a post via POST /blogs/posts, validating the slug with GET /blogs/posts/url-slug-exists, and confirming publication status.
POST /blogs/posts
title, content, slug, category, author
Trigger when Rankr drafts are updated to call PUT /blogs/posts/:postId.
Actions include updating post content via PUT /blogs/posts/:postId, and re-checking slug with GET /blogs/posts/url-slug-exists.
PUT /blogs/posts/:postId
postId, title, slug, content
Trigger on publish to ensure slug is unique and category mappings are valid.
Actions include slug existence check GET /blogs/posts/url-slug-exists and category fetch GET /blogs/categories and author fetch GET /blogs/authors.
GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors
slug, category, author
No-code automation lets you map fields and trigger actions without writing any code.
Faster publishing workflows reduce time to market for new content.
Centralized content governance ensures consistency across channels.
This glossary explains the core concepts used when linking the Blogs API with Rankr, including endpoints, slugs, webhooks, and authentication.
A defined URL path and HTTP method used to interact with an API.
A URL-friendly string derived from the post title that appears in the web address.
A lightweight callback that notifies systems when an event occurs.
An authorization framework that issues tokens to access resources without sharing passwords.
Automatically pull drafts from Rankr and publish via the Blogs API to your blogging platform.
Generate SEO metadata and validate slugs before publishing posts through the API.
Sync Rankr’s content calendar with Blog posts to schedule automatic publications.
Create a Rankr service integration and authorize access to the Blogs API endpoints.
Map Rankr fields to Blogs API post fields such as title, content, slug, category.
Run tests to ensure posts create and update correctly, then enable automation.
The Blogs API is a structured set of endpoints that allows you to manage blog content from Rankr. By connecting Rankr to the Blogs API you can push drafts, publish posts, and update content without leaving your workflow. Authentication uses API keys and OAuth tokens to secure requests and validate permissions. Once connected, you can map Rankr fields to blog post fields for a seamless publish experience. In practice, you’ll set up a service integration in Rankr, authorize the connection to the Blogs API, and start with a basic publishing flow that creates posts and checks slugs before going live.
No code is required to run the core publishing flow, thanks to the no-code automations built around the endpoints. You configure triggers and actions in Rankr to call the Blogs API endpoints. If your team needs custom logic beyond the built-in mappings, you can still extend the workflow with additional steps, but the standard use case can be achieved entirely through the UI. For more advanced scenarios, consider adding conditional logic and data enrichment steps that pull author or category metadata before publishing.
For basic publishing you typically need POST /blogs/posts to create content and GET /blogs/posts/url-slug-exists to ensure the slug is unique. You may also use PUT /blogs/posts/:postId to update posts after creation. These endpoints cover the essential publishing lifecycle from draft to live post. Additional endpoints like GET /blogs/categories and GET /blogs/authors help enrich posts with metadata.
Slug conflicts are handled by validating the slug before create or update using GET /blogs/posts/url-slug-exists. If the slug exists, you can automatically generate a unique slug or prompt for a different title. Maintaining a slug strategy in Rankr and ensuring proper slug checks prevents duplicate URLs and preserves SEO rankings. You can also implement a small fallback that appends a timestamp or a sequence number to the slug when conflicts are detected.
Scheduling is supported through the Blogs API by leveraging post scheduling fields or by triggering publish actions at a set time in Rankr. Depending on your setup, you can create or update a post and set a publish date that activates at a future time. This enables your content calendar to drive automatic publication without manual intervention. If scheduling is required beyond the API’s native capabilities, you can route a calendar cue via Rankr to trigger the appropriate publish endpoint at the scheduled moment.
API credentials are generated in the Blogs API dashboard. You’ll typically obtain an API key and configure OAuth client credentials. Store these securely in Rankr’s service integration settings, rotate them on a regular schedule, and limit scopes to only what is needed for your publishing workflow. Test credentials in a staging environment before going live.
You can sync core post data like title, content, slug, category, and author between Rankr and the Blogs API. You can also pull metadata such as categories and author profiles to enrich posts. For more advanced syncing, you can bring in SEO-related fields and publish status to ensure consistency across platforms.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
