Authenticate Rankr to your Blogs API project using an API key with the required scope emails/builder.readonly. Store credentials securely and rotate keys regularly.
Rankr uses the API key from your Blogs API dashboard to authorize requests. Grant the necessary scopes, then configure your app to pass the key in each request header.
GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; GET /blogs/categories; GET /blogs/posts/url-slug-exists; POST /blogs/posts; POST blogs/post; PUT /blogs/posts/:postId; PUT /blogs/posts/:postId; blogs/post-update.write; blogs/check-slug.readonly; blogs/category.readonly; blogs/author.readonly; GET /blogs/authors
Trigger: when a new draft is created in Rankr
Actions: POST /blogs/posts to publish, assign title, content, slug, author and category
POST /blogs/posts
title, content, slug, authorId, categoryId, status
Trigger: updates from Rankr reflect in existing posts
Actions: PUT /blogs/posts/:postId to update title, content, slug, and category
PUT /blogs/posts/:postId
postId, title, content, slug, categoryId
Trigger: changes in Rankr categories or authors sync with API data
Actions: GET /blogs/categories, GET /blogs/authors to keep metadata up-to-date
GET /blogs/categories; GET /blogs/authors
categoryId, name; authorId, name
Faster content workflows with automated publishing
Single source of truth for posts, categories, and authors
Reduced manual data entry and fewer errors
Key elements include endpoints, authentication, triggers, actions, and data mappings between Blogs API and Rankr.
A set of rules that allows Rankr to interact with Blogs API resources.
A specific URL path used to perform an operation in the Blogs API.
A URL-friendly version of a blog post title used in URLs.
Process of proving identity to access the Blogs API typically via API key or token.
Automatically publish new Rankr drafts to Blogs API with metadata to ensure visibility.
Use the Blogs API to publish posts to multiple channels on a schedule.
Track changes and maintain version history by updating posts via API.
Request access, generate a key, and grant scope emails/builder.readonly.
Map Rankr fields to Blogs API endpoints such as blogs/posts and blogs/categories.
Run tests, verify responses, handle errors, and enable automation.
Rankr can create, update, and manage blog content using the Blogs API. You can trigger new posts from Rankr events and publish them via the API endpoints. Additionally, you can fetch categories, authors, and check slug availability to avoid duplicates.
No extensive coding is required if you use the app connector. The integration uses standard HTTP requests with your API key and the necessary scopes. Configure a connection once and automate later steps.
Key endpoints include POST /blogs/posts for creation, PUT /blogs/posts/:postId for updates, and GET /blogs/categories plus GET /blogs/authors for metadata. You may also need GET /blogs/posts/url-slug-exists to prevent duplicates.
Authentication is via an API key from your Blogs API dashboard and the required scope. Pass the key in request headers and store it securely. Rotate keys periodically for security.
Categories are retrieved with GET /blogs/categories and authors with GET /blogs/authors. Map Rankr fields to categoryId and authorId to ensure accurate metadata during post creation.
Rate limits depend on your plan. Implement exponential backoff for failed requests and monitor quotas. If limits are reached, consider upgrading or splitting workloads.
See the Blogs API reference in your help center for endpoint details, payload examples, and error codes. You can also contact support for guidance and best practices.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
