Access requires a secure API key or OAuth token with the emails/builder.readonly scope to work with blogging and email-building endpoints.
Rankr authenticates to the Blogs API using your API key, ensuring requests stay within your allowed permissions.
Endpoints include: GET emails/builder; POST emails/builder; POST /emails/builder/data; 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/check-slug.readonly.
Trigger: a new blog post is published in Blogs API.
Actions: pull post details via GET /blogs/posts (where available), push to Rankr records, and trigger email campaigns.
Methods: POST /blogs/posts to create, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to verify slug.
Key fields: postId, slug, title, authorId, date.
Trigger: a new email is added or updated in emails/builder.
Actions: submit validation data via POST /emails/builder/data, store results, and segment campaigns.
Methods: POST /emails/builder/data for validation data; GET emails/builder to check status.
Fields: locationId, templateId, validationResult.
Trigger: new or updated categories/authors in Blogs API.
Actions: fetch categories and authors (GET /blogs/categories, GET /blogs/authors) and update Rankr taxonomy.
Methods: GET /blogs/categories, GET /blogs/authors.
Fields: categoryId, authorId, name, slug.
Automate repetitive tasks without writing code.
Orchestrate data flows across systems with visual workflows.
Reduce error-prone manual data entry and improve accuracy.
A concise glossary of API terms and the data flows used in this integration.
Application Programming Interface: a defined set of rules that allow apps to communicate.
HTTP method used to create a resource on the server.
HTTP method used to retrieve data from an endpoint.
A specific URL on an API where an action can be performed.
Automatically push new blogs to subscriber campaigns using POST /blogs/posts to publish, then trigger emails via POST /emails/builder/data or pull subscriber lists with GET /emails/builder.
Validate subscriber emails and route them to the right campaigns using POST /emails/builder/data and segment rules.
Sync categories and authors from Blogs API to Rankr for smarter tagging using GET /blogs/categories and GET /blogs/authors.
Register your API key and configure scopes (for example, emails/builder.readonly).
Select endpoints such as POST /blogs/posts, GET /blogs/categories, and POST /emails/builder/data.
Create workflows in Rankr that trigger on blog events or email validations.
The Blogs API provides programmatic access to manage blog content, categories, and authors. It enables you to create, fetch, update, and validate posts and associated data. Use the authentication steps described to securely call endpoints and retrieve or modify data as needed.
Rankr is the automation app that connects Blogs API data to downstream services to orchestrate workflows without code. With Rankr, you can build no-code automations that publish posts, validate emails, and sync taxonomy across systems. This page focuses on how to leverage those capabilities for a smooth integration between Blogs API and Rankr.
For blog posts, use POST /blogs/posts to create and PUT /blogs/posts/:postId to update an existing post. You can verify slug availability with GET /blogs/posts/url-slug-exists. For taxonomy and authors, use GET /blogs/categories and GET /blogs/authors to pull the latest data into Rankr.
Authentication generally uses an API key or OAuth token with the appropriate scopes (for example, emails/builder.readonly). Keep credentials secure, rotate keys regularly, and apply the principle of least privilege to your integration.
Yes. You can validate email data using the emails/builder endpoints. Submit validation payloads with POST /emails/builder/data and use the results to route contacts into correct campaigns without writing code.
Some endpoints require specific scopes to access. Ensure your API key or token includes the necessary scopes, such as emails/builder.readonly, to perform the actions in your workflow. Align scopes with the operations you plan to automate.
Test the integration in a sandbox or staging environment using test keys and dummy data. Validate responses, inspect logs, and gradually move to production once you confirm reliable behavior.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
