Use your GHL access token with the scope emails/builder.readonly to securely access blog data. Keep credentials secret and rotate them regularly.
Rankr authentication uses your app credentials and will obtain a token to call the Blogs API. Store credentials securely and rotate as recommended.
GET emails/builder; GET emails/builder.write; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; emails/schedule.readonly; GET emails/schedule; blogs/post.write; POST /blogs/posts; blogs/post-update.write; PUT /blogs/posts/:postId; blogs/check-slug.readonly; GET /blogs/posts/url-slug-exists; blogs/category.readonly; GET /blogs/categories; blogs/author.readonly; GET /blogs/authors
Trigger: when a new blog post is published via Blogs API, Rankr sends an SMS alert to subscribers.
Actions: create an SMS message, schedule delivery, and log the event.
POST /blogs/posts
Required fields: title, content, slug, author_id, published_at
Trigger: new posts are published, an email digest is generated.
Actions: queue emails via Emails Builder, send to a subscriber list, include a summary.
POST /emails/builder
Key fields: recipient_list, subject, body, templateId
Trigger: post status changes (e.g., draft to published)
Actions: update post status, notify via SMS, log update.
PUT /blogs/posts/:postId
Fields: postId, status, updated_at
Build powerful workflows in minutes with ready-to-use API endpoints and drag-and-drop automation.
Eliminate custom development while delivering timely SMS updates and blog notifications.
Keep content and messaging synced across your channels without leaving Rankr.
This glossary explains core elements and processes used to connect the Blogs API with Rankr, including endpoints, authentication, triggers, and actions.
Application Programming Interface — a set of endpoints you can call to read or write data in Blogs API.
A callback mechanism that delivers real-time updates to Rankr when an event occurs.
A specific URL that accepts requests to perform an operation in Blogs API.
A URL-friendly string derived from the post title used in blog URLs.
Aggregate the week’s posts and deliver a concise SMS digest to subscribers.
Notify editors when posts move through stages using SMS or internal messages.
Publish content via Blogs API and push a cross-post to social or email through Rankr.
Obtain an API key or OAuth token with the required scopes (emails/builder.readonly) from GHL.
In Rankr, set up a trigger for new blog posts to initiate SMS or email actions.
Run end-to-end tests, monitor logs, and adjust endpoints as needed.
The Blogs API provides endpoints to manage blog content, posts, categories, and authors, enabling you to read, create, update, and organize blog data from Rankr. This makes it possible to trigger actions such as SMS alerts or emails when new posts are published. By combining these capabilities with Rankr workflows, you can automate reader engagement without writing custom code. In practice, you’ll use the Blogs API endpoints to pull post details and status, then map those events to Rankr actions (SMS, emails, or internal notifications) to keep subscribers informed in real time.
For creating blog posts, the primary endpoints are POST /blogs/posts to publish new content, and GET /blogs/posts/url-slug-exists to ensure your slug is unique. You may also use PUT /blogs/posts/:postId to update existing posts and GET /blogs/authors or GET /blogs/categories to enrich posts with author and category data. These endpoints let Rankr drive content creation workflows and verify data consistency before distribution.
Authentication typically uses an OAuth token or API key with the required scopes (for example, emails/builder.readonly) included in your request. Include the token in the Authorization header when calling the Blogs API endpoints. Rotate credentials regularly and follow your security best practices to protect access to content and messaging workflows.
Yes. You can configure Rankr to send SMS alerts for new posts or updated posts using the relevant endpoints. Set up triggers in Rankr so that when a post is published or updated, an SMS message is queued or delivered to your subscriber list. This enables timely reader engagement without manual steps.
No-code is fully supported. Rankr’s visual workflows allow you to connect Blogs API endpoints to SMS and email actions without writing code. Advanced users can still leverage API calls directly, but you can achieve most use cases through drag-and-drop automation.
A slug is a URL-friendly string derived from the post title, used to form the post URL. It should be unique for each post. You can check slug availability with GET /blogs/posts/url-slug-exists before publishing.
If you need more connections beyond the top three, you can expand Rankr automations to include additional endpoints such as blog categories, authors, or the emails builder. This allows broader coverage, including category-based alerts, author-specific updates, and multi-channel messaging.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
