Authenticate securely with the Blogs API using API keys or OAuth based on your setup
Configure Rankr to store credentials safely and use access tokens when calling the Blogs API
Core endpoints include 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/posts
When a new post is published, fetch email templates from the Blogs API to automate notification emails
Use GET emails/builder to pull templates and POST /blogs/posts to publish updates
GET emails/builder
templateId, templateName, content
Creating or updating a blog post triggers a Rankr campaign update
POST /blogs/posts to create and PUT /blogs/posts/:postId to update
POST /blogs/posts
postId, title, slug, content, category
Changes to a blog post update the SEO fields via API
PUT /blogs/posts/:postId to update seoTitle seoDescription metaKeywords
PUT /blogs/posts/:postId
seoTitle, seoDescription, metaKeywords
Automate tasks without writing code using prebuilt endpoints and templates
Faster time to value with streamlined workflows and triggers
Centralized data flow between content management and campaigns
This glossary covers the core terms used in the Blogs API integration with Rankr and how data flows between systems
A specific URL path you call to perform an action
A mechanism to receive real time updates from the API
Methods used to verify identity and authorize API calls
Maximum number of requests allowed in a time window
Automatically generate and send email newsletters when a new post is published
Push post updates to Rankr campaigns and social channels
Populate SEO title and meta data using the API during publish
Register the app, obtain API keys and set scopes such as emails/builder.readonly
Create mappings between blog data and Rankr fields
Run tests, review logs, and deploy to production
Most setups use API keys or OAuth tokens to authorize calls. Store credentials securely in Rankr and rotate keys periodically. Use the scopes required for reading templates and posting blogs. This ensures only approved actions are allowed. Always follow the least privilege principle.
Common workflows involve retrieving email templates with GET emails/builder, creating posts with POST /blogs/posts, and updating posts with PUT /blogs/posts/:postId. You may also check slug availability with GET /blogs/posts/url-slug-exists and manage categories with GET /blogs/categories.
Yes. No code automation is possible using the prebuilt endpoints and Zapier style app connector. You can configure triggers and actions in Rankr to automate blog and email workflows without writing code.
Rate limits apply per API key or token. If you hit limits, spread requests over time, implement exponential backoff, and cache frequent lookups to reduce calls.
Map blog fields such as title slug content category to Rankr fields. Use endpoints to fetch slug existence, categories, and authors to enrich content in Rankr campaigns.
If a call fails, check the error response, retry with backoff, and verify authentication and endpoint availability. Set up monitoring and alerts for persistent issues.
Official API docs are available in the developer portal for the Blogs API. Look for integration guides, endpoint references, and authentication details.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
