To authorize requests to the Blogs API you’ll use the provided OAuth credentials. Scope: emails/builder.readonly. Keep tokens secure and rotate them regularly.
Rankr authenticates to the Blogs API using a standard OAuth 2.0 flow (client credentials). Use your client ID and secret, request the required scope, and exchange the authorization code for an access token.
– GET emails/builder — Retrieve email templates. – GET emails/builder.readonly — Access read-only templates. – POST emails/builder — Create a new email template. – POST /emails/builder/data — Submit template data for processing. – DELETE /emails/builder/:locationId/:templateId — Delete a specific template. – emails/schedule.readonly — Read-only access to scheduling data. – GET emails/schedule — Retrieve email scheduling information. – POST /blogs/posts — Create a new blog post. – PUT /blogs/posts/:postId — Update an existing blog post. – GET /blogs/posts/url-slug-exists — Check if a slug already exists. – GET /blogs/categories — List blog categories. – GET /blogs/authors — Retrieve author information.
Trigger: When Rankr needs to render or edit an email template during support workflows.
Actions: Call GET emails/builder to fetch templates and supply template data to your editor in Rankr.
GET emails/builder
templateId, locationId, name
Trigger: When new content is approved in Rankr, push to Blogs API to create a post.
Actions: Use POST /blogs/posts to create, set title, content, and publish date; ensure slug is valid.
POST /blogs/posts
title, content, slug, publishDate
Trigger: Update post status or content from Rankr as needed.
Actions: Update with PUT /blogs/posts/:postId to modify title, body, or status.
PUT /blogs/posts/:postId
postId, title, content, status
Build integrations without writing code by routing data between Blogs API and Rankr through ready-made endpoints.
Launch automations quickly with point-and-click configuration and webhooks.
Scale your content workflows by chaining endpoints like scheduling, categories, and authors.
Definitions and examples of API endpoints, tokens, scopes, data models, and how they fit into Rankr integrations.
A specific URL and HTTP method used to perform an action against the API.
A token used to authenticate requests securely and grant access to protected resources.
A set of permissions granted to an access token, defining what actions are allowed.
A URL that receives real-time HTTP notifications when events occur.
Automatically push new Rankr posts to the Blogs API when approved for publication.
Pull email templates from Blogs API to power Rankr email campaigns.
Validate slugs before publishing to prevent duplicates and improve SEO.
Map templates, posts, and related metadata between Blogs API and Rankr before enabling automation.
Configure OAuth credentials, request the required scope, and test endpoints like GET emails/builder and POST /blogs/posts.
Review logs, adjust rate limits, and add more endpoints as your workflow grows.
In most setups you do not need a separate account beyond your existing GHL and Rankr accounts. Access is controlled via API keys or tokens tied to your organization. The Blogs API scope (emails/builder.readonly) determines what you can view or modify. Ensure your app is authorized so Rankr can perform the required actions. Additionally, maintain least-privilege access by granting only the necessary scopes for the workflow.
Scopes define what an access token can do. For this connection, the recommended scope is emails/builder.readonly to read templates and manage posts. If you require writing capabilities, your OAuth setup must explicitly request the appropriate write scope. Always adhere to the principle of least privilege and rotate tokens regularly.
Yes. Use a development or sandbox environment when available to validate connections without impacting production data. Test common flows such as fetching templates (GET emails/builder) and creating posts (POST /blogs/posts). Use mock data to confirm payloads, responses, and error handling.
Store OAuth tokens securely on your server (not in the client). Use environment variables and secret management, rotate tokens on a schedule, and implement token revocation handling. Never expose tokens in client-side code or logs.
If an endpoint returns an error, review the HTTP status code, error message, and the request payload. Check token validity and scope, endpoint permissions, and rate limits. Use retry/backoff where appropriate and consult the integration logs for detailed diagnostics.
Rate limits vary by plan and endpoint. Expect possible throttling on high-traffic bursts. Implement exponential backoff, and monitor response headers for remaining quota. If you consistently hit limits, consider batching requests or upgrading your plan.
Yes. The docs include sample payloads for common actions like creating posts and templates. Start with minimal examples to verify structure (title, content, slug) and then expand to include additional fields as needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
