Authenticate to the Blogs API using OAuth 2.0 or API keys, and assign the necessary scopes to access blog creation, updates, categories, and authors.
Rankr securely authenticates to Blogs API via OAuth client credentials or API keys. Keep credentials stored securely and rotate them regularly.
Key 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, POST /blogs/posts, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts/url-slug-exists, GET /blogs/posts, GET /blogs/categories, GET /blogs/authors.
Trigger: when a new draft is ready in Rankr, publish it via POST /blogs/posts.
Actions: create post, set slug, assign author and category, publish to blog.
Methods/Paths: POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists.
Key fields: postId, title, content, slug, authorId, categoryId.
Trigger: updates to a blog post in Blogs API trigger a refresh in Rankr.
Actions: update post, propagate changes to Rankr records and subscribers.
Methods/Paths: PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists.
Key fields: postId, slug, updatedAt.
Trigger: schedule times or triggers when Rankr sends content to email campaigns.
Actions: schedule posts, trigger emails, push summaries via emails and blogs.
Methods/Paths: POST /emails/builder/data; GET emails/builder; POST /blogs/posts.
Key fields: postId, scheduleTime, recipientList.
No code required: publish posts directly from a visual workflow.
Automations save time: schedule posts and automate workflows without writing code.
Consistency and accuracy: a single source of truth for blog content and campaigns.
This glossary defines terms and processes used when integrating Blogs API with Rankr.
Application Programming Interface; a set of endpoints that let you create, fetch, update, and delete blog content via the Blogs API.
Authorization framework used to grant Rankr access to Blogs API without sharing user credentials.
A URL-friendly version of a post title used in the final blog URL.
A callback URL that Blogs API uses to notify Rankr about events like new posts or updates.
Automate weekly roundup posts by pulling drafts from Rankr and publishing via Blogs API.
Use GET /blogs/posts/url-slug-exists to ensure unique slugs and suggest SEO friendly alternatives.
Publish to Rankr and push summaries to email campaigns automatically.
Create a new client in Blogs API and copy the client ID and secret.
Complete OAuth flow or use API keys with the required scopes.
Test POST /blogs/posts, GET /blogs/categories, and GET /blogs/posts/url-slug-exists to ensure everything works.
To connect Blogs API with Rankr, you need appropriate access permissions via OAuth or API keys with scopes that cover blog creation, updates, categories, and authors. Start by obtaining a client ID and secret from Blogs API and assign the necessary scopes. Test the connection in a controlled environment before going live. The combination of correct credentials and scopes ensures secure and successful interactions between Rankr and Blogs API.
Yes. Rankr can publish blog posts directly to Blogs API using the POST /blogs/posts endpoint. You can prepare drafts in Rankr, map fields like title, content, slug, and author, and push them to your blog. This enables a no-code workflow from content creation to live publishing.
Use the GET /blogs/posts/url-slug-exists endpoint to verify slug availability. If the slug is taken, you can retry with a new slug or implement a slug generation strategy. This helps prevent duplicate URLs and maintains clean SEO-friendly paths.
Essential endpoints include POST /blogs/posts for creating posts, PUT /blogs/posts/:postId for updates, GET /blogs/posts/url-slug-exists for slug checks, and GET /blogs/categories and GET /blogs/authors for metadata. Depending on your workflow, you might also use GET /blogs/posts to retrieve content and DELETE endpoints for removal.
Scheduling is typically handled by Rankr through its automation features. You can queue posts with a scheduleTime and use the Blogs API to publish at the specified time, enabling steady content distribution without manual intervention.
Yes. Blogs API supports multiple authors and categories. You can fetch author metadata using GET /blogs/authors and categories using GET /blogs/categories, then assign posts accordingly during creation or updates.
For more templates and examples, consult the Blogs API documentation and the Rankr integration hub. You can also explore sample workflows and community templates that demonstrate common use cases like post publishing, updates, citations, and SEO optimization.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
