Authenticate using your Blogs API credentials. Choose OAuth 2.0 or an API key and grant Rankr the minimum scopes needed (emails/builder.readonly, blogs/post.write, blogs/post-update.write, and blogs/check-slug.readonly).
Rankr securely stores your access tokens and automatically refreshes them as needed while making API calls to the Blogs API endpoints listed below.
Emails: GET emails/builder, POST emails/builder, POST /emails/builder/data; Schedules: emails/schedule (GET), GET emails/schedule; Blogs: POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, GET /blogs/categories; Slug checks: GET /blogs/posts/url-slug-exists
Trigger: A new post is published in Blogs API and a corresponding email draft is created in Rankr to notify subscribers.
Actions: create email draft (POST emails/builder), schedule send (GET emails/schedule), and publish the blog post (POST /blogs/posts) when ready; map postId and slug accordingly.
Method paths to implement: POST emails/builder, POST /blogs/posts, GET emails/schedule
Key fields: postId, locationId, templateId, slug, status
Trigger: A new post is added in a specific category; Rankr sends a category-specific digest via Blogs API.
Actions: fetch categories (GET /blogs/categories), fetch author details (GET /blogs/authors), assemble email content (POST emails/builder) and schedule (POST /emails/builder/data).
Method paths: GET /blogs/categories, GET /blogs/authors, POST emails/builder
Fields: categoryId, authorId, slug, postId
Trigger: Email sends complete; collect open/click metrics and adjust upcoming campaigns in Rankr.
Actions: read email performance (GET emails/builder, GET emails/schedule), push insights to Rankr dashboards; optionally update posts based on results (PUT /blogs/posts/:postId).
Method paths: GET emails/builder, GET emails/schedule, PUT /blogs/posts/:postId
Fields: sendId, openRate, clickRate, postId
No-code automation to create, publish and send blog content without writing a single line of code.
Seamless data syncing between Blogs API and Rankr improves consistency and saves time.
Prebuilt triggers, actions and endpoints enable rapid experimentation and faster results.
This glossary covers API endpoints, authentication, triggers, actions, and data mapping used in the Blogs API and Rankr integration.
An accessible URL that performs a specific action when called by Rankr or the Blogs API.
A callback URL that receives real-time updates when events occur in the Blogs API.
The process of verifying identity and granting access to an API.
A URL-friendly string used in post URLs and SEO.
On signup, automatically create a welcome sequence that highlights recent posts from Blogs API.
Publish a digest email of new posts on a schedule using Blog API data.
Segment subscribers by preferred categories and send tailored content.
Obtain client ID and secret for the Blogs API and store securely in Rankr.
Use OAuth 2.0 to obtain access tokens with required scopes (emails/builder.readonly).
Map endpoints to Rankr actions and run tests to verify data flow.
Yes. Use OAuth 2.0 with token-based authentication to securely connect. Store tokens safely and refresh them before expiry. Rankr passes the required scopes to access emails and blog resources. This setup minimizes exposure and keeps data safe. Additionally, enable IP whitelisting if supported by the Blogs API for extra security.
For basic outbound emails, you will typically call GET emails/builder to pull email templates, POST emails/builder to create drafts, and POST /emails/builder/data to populate and send. You may also use GET emails/schedule to plan sends. These endpoints cover draft creation, scheduling, and publishing.
Yes. Rankr can publish posts directly by calling POST /blogs/posts when you have a post ready. You can pass content, slug, and category data if required. This enables a seamless publishing workflow from Rankr to your blog.
Test the connection by running a small campaign, verifying token validity, and confirming that blog posts and emails appear as expected. Use the endpoints list to run a dry run and check response codes and data mapping.
Synced data typically includes posts (title, slug, status), categories, authors, and email templates or campaign details. Set up mapping rules to sync only what you need for campaigns to avoid duplication.
Yes. Rate limits vary by endpoint; plan with throttling in Rankr and implement exponential backoff. If you exceed quotas, use batch processing where supported or stagger requests.
Visit the official Blogs API docs at the provider’s site. In Rankr, you can access a consolidated docs panel with endpoint references for emails, blogs, and authors.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
