Start by obtaining an API key for the Blogs API and assign the scope emails/builder.readonly. Store credentials securely and rotate keys regularly to protect your integration.
Use Rankr to authorize the Blogs API connection. Follow the OAuth flow or API key setup to grant the necessary permissions for post creation, updates, and category access.
Endpoints powering the Cloud Attract flow include GET emails/builder, POST emails/builder/data, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, and GET /blogs/posts/url-slug-exists among others. These endpoints enable post creation, updates, slug checks, category and author retrieval, and email integration within Rankr.
Trigger when a new content item is ready in Rankr to publish to Blogs API
Actions include creating the post, mapping title and content, assigning categories, and setting the slug
POST /blogs/posts
Title, Content, Slug, Categories, AuthorId, PublishedDate
Trigger when Rankr detects a post update and needs to sync with Blogs API
Actions include updating content or slug and refreshing post metadata
PUT /blogs/posts/:postId
PostId, Title, Slug, Content, Categories
Trigger before publish to verify slug uniqueness using blogs/check-slug.readonly and GET /blogs/posts/url-slug-exists
Actions ensure slug uniqueness, attach categories, and align author data
GET /blogs/posts/url-slug-exists
Slug, PostId, CategoryIds
No code required to automate publishing and updating blog posts from Rankr to the Blogs API, reducing time and human error
Unified workflows across email, blog content, and campaigns without custom development
Real time updates and insights visible in Rankr dashboards for faster decision making
This glossary defines the core terms used to connect Blogs API with Rankr, including endpoints, posts, slugs, categories, authors, and triggers
An Application Programming Interface that lets Rankr interact with the Blogs API to perform actions like create, update, and fetch data
A URL friendly identifier for a blog post used in routing and SEO
A specific URL in the Blogs API that performs a defined operation such as create or retrieve data
An event in Rankr that starts an automation to call a Blogs API endpoint
Set up a workflow that pushes a new Rankr content item directly to the Blogs API when ready, mapping title, body, slug and metadata automatically
Validate slug uniqueness prior to publishing to avoid duplicates and lost SEO value
Automatically mirror published blogs to social channels or newsletters via Rankr workflows
Step 1 is to authorize the Rankr account to access the Blogs API using your API key and OAuth credentials
Step 2 involves selecting endpoints and assigning scopes such as emails/builder.readonly and blog write permissions
Step 3 is to run test calls in a staging environment, verify data accuracy, and then enable live syncing
Blogs API provides programmatic access to create, update, and fetch blog content. When connected to Rankr, you can automatically push new content to your blog, update existing posts, and manage metadata without writing code. This enables faster content workflows and tighter alignment with campaigns.
For posting and updating blogs you will typically use POST /blogs/posts to create, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to verify slug availability. You may also use POST /blogs/post-update.write for incremental updates and GET /blogs/categories to fetch categories.
Slug existence can be checked with GET /blogs/posts/url-slug-exists or by using blogs/check-slug.readonly ahead of publishing. This helps prevent duplicate URLs and preserves SEO value.
Yes. You can fetch blogs categories and authors with endpoints such as GET /blogs/categories, GET /blogs/authors, and GET /blogs/author.readonly, enabling you to map taxonomy and author data during content creation.
Authentication typically involves an API key with defined scopes plus any OAuth flow required by your setup. Keep credentials secure and rotate keys regularly. The scope for blogging actions is usually related to post creation and category access.
Images and media can be attached as part of the post payload or via separate media endpoints depending on the Blogs API. Ensure your Rankr workflows map media fields correctly and respect file size and type limits.
Rankr provides logs and activity reports for the Blogs API integration. If an API call fails, check error messages, verify credentials, review endpoint permissions, and retest in a staging environment before going live.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
