To access the Blogs API from Rankr, generate an API key with the required scope: emails/builder.readonly. Store secrets securely in Rankr and rotate keys regularly.
Use API keys or OAuth to authorize Rankr to access Blogs API. Follow Rankr security guidelines and test in a staging environment.
– GET emails/builder; – POST emails/builder; – POST /emails/builder/data; – DELETE /emails/builder/:locationId/:templateId; – GET emails/schedule; – POST /blogs/posts; – PUT /blogs/posts/:postId; – GET /blogs/posts/url-slug-exists; – GET /blogs/categories; – GET /blogs/authors; – GET /blogs/check-slug.readonly
Trigger: A new blog draft is created in Rankr
Action: POST /blogs/posts to publish the draft as a blog post
POST /blogs/posts
title, content, slug, categoryId, authorId, status
Trigger: Rankr detects an edited post
Action: PUT /blogs/posts/:postId to apply updates
PUT /blogs/posts/:postId
postId, title, slug, content, categoryId, authorId
Trigger: Publish or schedule toggle
Actions: Check slug availability with GET /blogs/posts/url-slug-exists, then set slug and publish
GET /blogs/posts/url-slug-exists
slug, postId
No-code automation reduces manual data entry and accelerates publishing.
Rapid syncing of blog content with marketing emails and campaigns.
Visual workflow builders enable fast iteration without writing code.
Definitions for core terms used throughout this guide.
A set of endpoints and methods that let Rankr access the Blogs API programmatically.
A specific URL and method within an API used to perform an action.
A URL-friendly identifier derived from the post title.
An authorization framework that lets Rankr securely access the Blogs API without sharing credentials.
Turn campaign briefs into blog drafts automatically in Blogs API when a new Rankr campaign starts.
Pull author and category data from Blogs API into Rankr to enrich posts and campaigns.
Validate and reserve slugs before publishing to avoid duplicates.
Obtain API keys with the correct scopes and connect them in Rankr’s API settings.
Map Rankr triggers to Blogs API endpoints and set up the required field mappings.
Run end-to-end tests, verify slug checks, and go live with monitoring.
No coding is required for the core flow. Rankr’s no-code builder lets you connect triggers to Actions using the Blogs API endpoints. Start with a simple post-creation workflow and expand as needed. If you’re comfortable with basic webhooks, you can extend automation further, but it’s not mandatory.
Use POST /blogs/posts to create new posts and PUT /blogs/posts/:postId to update existing ones. For slug validation, rely on GET /blogs/posts/url-slug-exists before publishing. You can also fetch categories and authors with GET /blogs/categories and GET /blogs/authors to enrich posts.
Slug existence is checked with GET /blogs/posts/url-slug-exists. If the slug is taken, adjust the post title or slug and recheck until a unique URL is returned. This prevents duplicate posts and broken links.
Use HTTPS, rotate API keys regularly, and store credentials in Rankr’s secure vault. Restrict scopes to the minimum needed (e.g., emails/builder.readonly for reading templates) and monitor access logs for unusual activity.
Yes. You can map title, content, slug, categoryId, authorId, and status fields from Rankr to the Blogs API. This ensures your posts retain consistent metadata across platforms and campaigns.
Check endpoint responses for error codes, verify API keys and scopes, and ensure required fields are provided. Use test posts in a staging environment, then gradually promote to production with monitors and alerts.
Endpoint usage is visible in Rankr’s integration logs. You’ll see call counts, success/failure rates, and rate limits. If you hit quotas, adjust polling frequency or batch requests to stay within limits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
