Use OAuth tokens or API keys issued by the Blogs API to authorize requests from Rankr. Keep credentials secure and refresh tokens as required.
Configure Rankr to securely store and present the API credentials, using OAuth 2.0 flows or API keys as supported by Blogs API.
Key endpoints include: GET emails/builder; POST /emails/builder; 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/categories (readonly); GET /blogs/authors (readonly).
Trigger: when a new draft is ready in Rankr, a post is created in Blogs API.
Actions: call POST /blogs/posts to publish content with metadata like title, slug, category, and author.
POST /blogs/posts
title, content, slug, category_id, author_id, status
Trigger: an edit to a Rankr draft triggers PUT /blogs/posts/:postId to update the published post.
Actions: update title, content, and slug in Blogs API; adjust status as needed.
PUT /blogs/posts/:postId
postId, title, slug, content, category_id, author_id
Trigger: changes in categories or authors in Blogs API should propagate to Rankr mappings.
Actions: create/update categories and authors in Rankr to keep mappings current.
GET /blogs/categories
categoryId, name, slug; authorId, name
Automation of content publishing reduces manual steps and speeds up workflows.
Real-time data synchronization ensures posts, categories, and authors stay up to date.
No-code setup means faster onboarding for teams and easier maintenance.
This section defines API, endpoints, authentication, triggers, and data mapping used to connect Rankr with Blogs API.
An Application Programming Interface that lets Rankr communicate with the Blogs API to read and write data.
The process of validating requests using OAuth tokens or API keys before granting access.
A URL-friendly string derived from a post title used in the web address.
A specific route within an API used to perform an action, such as POST /blogs/posts.
Feed Rankr a concise brief and have Blogs API draft a post ready for review and publication.
Coordinate release times with marketing calendars using Rankr and Blogs API.
Route content to different blog categories in Blogs API based on Rankr insights.
Register the Blogs API integration in Rankr and generate API keys.
Configure OAuth or API keys in Rankr and test authentication.
Choose endpoints, map data fields, and run verification tests.
In most setups, no coding is required. Rankr provides a visual workflow to connect to Blogs API endpoints. You can authenticate and map fields without writing code. If you have an existing automation, you can reuse webhooks or create custom steps using API keys.
Essential endpoints for basic publishing include creating posts (POST /blogs/posts), updating posts (PUT /blogs/posts/:postId), and checking slug availability (GET /blogs/posts/url-slug-exists). You may also fetch authors and categories as needed.
Authentication is typically handled via OAuth 2.0 tokens or API keys. In Rankr, configure credentials and test by making a simple request to a test endpoint. Store tokens securely and rotate them as required.
Yes. You can update content after publishing using PUT /blogs/posts/:postId. You can modify title, body, slug, and related metadata, and re-publish as needed.
Slug checks are automatic when creating posts. Use GET /blogs/posts/url-slug-exists to verify uniqueness before finalizing a post URL.
Rankr can sync authors and categories by pulling lists from Blogs API (GET /blogs/authors and GET /blogs/categories) and keeping your mappings up to date.
Test the connection in Rankr using a sandbox or test mode, verify authentication, and run a small publishing workflow to confirm end-to-end data flow.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
