Use the API keys or OAuth tokens provided by Blogs API to authorize requests from Rankr. Store credentials securely and rotate keys regularly.
Rankr authenticates with Blogs API using your account credentials and an API key to securely perform actions like publishing posts and sending notifications. Keep these credentials confidential.
– GET emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – GET emails/schedule – blogs/post.write – POST /blogs/posts – PUT /blogs/posts/:postId – GET /blogs/posts/url-slug-exists – GET /blogs/categories – GET /blogs/authors
When a new blog post is published in Blogs API, Rankr automatically sends a WhatsApp notification to subscribers.
Actions include publishing the post via POST /blogs/posts, validating the slug with GET /blogs/posts/url-slug-exists, and sending a formatted WhatsApp message.
POST /blogs/posts
title, content, slug, author, published_at
When a blog post is updated in Blogs API, Rankr sends an update notification to the WhatsApp channel.
Update the post via PUT /blogs/posts/:postId, refresh the slug if changed, and push a notification with changes.
PUT /blogs/posts/:postId
postId, updatedFields, timestamp
Before publishing, Rankr checks slug availability to avoid duplicates.
Check slug with GET /blogs/posts/url-slug-exists, publish if available, then notify via WhatsApp.
GET /blogs/posts/url-slug-exists
slug, exists
Faster time-to-value with drag-and-drop setup, no coding required.
Scalable automation for large subscriber lists with consistent messaging.
Easy testing and iteration using live previews and sandbox data.
This glossary defines common terms used in the Blogs API and Rankr integration to help you understand the workflow.
A specific URL and HTTP method that enables a defined function in an API.
A callback URL that receives real-time data events from an external service.
A URL-friendly identifier derived from the post title for clean URLs.
The process of verifying identity and granting access to API resources.
Automatically push a daily digest of new posts to WhatsApp subscribers via Rankr.
Share draft posts with a small test group before public publishing to gather feedback.
Cross-promote blog content within WhatsApp messages to boost engagement and discoverability.
Collect your Blogs API key or OAuth token and set up Rankr with the appropriate scopes to access posts and notifications.
Choose endpoints like POST /blogs/posts and GET /blogs/posts/url-slug-exists, then map fields such as title, excerpt, and slug to the WhatsApp message content.
Run tests in Rankr, verify messages, and then deploy to your live WhatsApp channel with monitoring.
To connect Blog API to Rankr, you’ll need an API key or OAuth credentials from Blogs API, plus a Rankr account with the Blogs API integration enabled. Store credentials securely and configure any required scopes to access posts and messaging endpoints. Once set up, test a simple publish-to-WhatsApp flow to confirm connectivity. Tip: Rotate credentials periodically and use least-privilege access to reduce risk.
Required endpoints typically include creating posts (POST /blogs/posts) and slug validation (GET /blogs/posts/url-slug-exists), along with the messaging trigger (to send WhatsApp alerts). In some setups you’ll also pull post metadata (title, excerpt) and publish status. Start with a minimal flow and expand as needed. Remember to secure calls with your API key and keep payloads minimal for reliability.
Use Rankr’s test mode or a sandbox channel to simulate posts and watch WhatsApp messages appear as expected. Validate fields such as title, slug, and excerpt, and monitor delivery status in Rankr’s logs. Iterate until messages render correctly on all devices. Pro tip: Enable verbose logging temporarily while testing.
Yes. You can customize the message template, including the title, summary, and a link to the full post. Use placeholders for dynamic fields and preview changes in Rankr before enabling production delivery. Consider adding fallback text and emoji to improve readability on WhatsApp.
Rate limits depend on your Blogs API plan and Rankr’s usage policies. If you hit quotas, spread requests over time or cache results. Contact support to discuss higher limits if your integration requires it. Best practice is to implement exponential backoff and retry handling.
Rankr provides a logs dashboard and webhook diagnostics to monitor the flow from Blogs API to WhatsApp. Check request/response payloads, success/failure counts, and timestamps. Use filters to pinpoint errors and re-run failed items. Enable alerting for critical failures so teams are notified immediately.
Slug checks can fail if the slug is already in use or if there’s a temporary API outage. Verify the slug with GET /blogs/posts/url-slug-exists before publishing, handle conflict responses gracefully, and provide a meaningful message to users. Retry logic helps during transient outages. Maintain a short slug length and avoid special characters to improve reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
