Authenticate with OAuth 2.0 tokens and Rankr client credentials. Include the scope emails/builder.readonly to access email templates.
In Rankr, configure a secure API key or OAuth flow to authorize access to Blogs API endpoints.
Key endpoints used within this integration include email management and blog publishing: GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, GET blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, GET /blogs/categories, GET /blogs/posts, etc. These endpoints enable creating, updating, scheduling, and validating blog content and email templates within the Rankr workflow.
Trigger: A new draft is ready in Rankr and should be published in Blogs API.
Actions: create or update a post in Blogs API using POST /blogs/posts or PUT /blogs/posts/:postId; notify stakeholders via emails/builder.
Method/Path: POST /blogs/posts or PUT /blogs/posts/:postId
Key fields: title, content, slug, postId, status
Trigger: new or updated post that should be emailed to subscribers.
Actions: send emails via emails/builder with templates, or publish to blogs.
Method/Path: GET /blogs/posts/url-slug-exists, POST /blogs/posts
Key fields: slug, title, author, publishDate
Trigger: sync failures or endpoint errors.
Actions: log errors in Rankr, trigger alerts, and retry with backoff.
Method/Path: GET /blogs/posts, GET /blogs/categories
Key fields: errorCode, message, endpoint, timestamp
No-code automation: connect endpoints via visual builders and triggers.
Faster implementation with drag-and-drop workflows and templates.
Scalability and reliability through cloud-based endpoints and retries.
This glossary covers API concepts like endpoints, authentication, webhooks, slug checks, and data fields used by Blogs API and Rankr.
An Application Programming Interface that enables Rankr and Blogs API to communicate and exchange data securely.
A lightweight HTTP callback used to notify Rankr of events like new posts or updates in Blogs API.
A specific URL in Blogs API that performs a defined action, such as retrieving posts or creating a post.
A URL-friendly version of a post title used to build human-readable and SEO-friendly links.
Automatically generate, schedule, and publish content based on campaigns using endpoints.
Use subscriber data to tailor posts and topics for higher engagement.
Trigger notifications when posts are published or updated.
Register a client in Blogs API, note client ID and secret in Rankr.
Complete OAuth flow and ensure emails/builder.readonly scope is granted.
Associate the endpoints you plan to use with Rankr automations and run tests.
The Blogs API lets you manage emails and blog content through a secure interface. You can pull templates, schedule emails, create blog posts, and manage categories. With Rankr, automation becomes possible without writing code, linking campaigns to post publishing and email workflows. This combination enables you to streamline content production and distribution across channels.
Authentication uses OAuth 2.0 tokens and Rankr credentials. Ensure scopes include emails/builder.readonly to access email templates. Store tokens securely, refresh as needed, and rotate credentials regularly to maintain access.
Choose endpoints based on your use case. For publishing, use blogs/posts endpoints; for slug validation, use GET /blogs/posts/url-slug-exists; for categories and authors, use blogs/category.readonly and blogs/author.readonly. Combine endpoints with Rankr automations to tailor workflows to campaigns.
No-code builders can set up most automations, using templates and triggers. Some advanced payloads may require lightweight scripting or custom fields in Rankr.
Endpoint rate limits vary by service. Plan for bursts and implement exponential backoff retries. Monitor API usage and adjust workflows to stay within limits.
Test in a staging environment with sample data. Validate responses, error handling, and retry logic before going live.
Check Rankr and Blogs API dashboards for logs. Enable webhooks to receive live event data and set up alerts for failures or delays.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
