Authenticate the Blogs API from your Rankr workspace by generating an API key or OAuth token and granting access to the required endpoints.
Store your API credentials securely in Rankr and attach them to the OneSignal integration so content actions are performed under a secure, authenticated session.
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
Trigger: a new or updated article in Rankr prompts a post to the Blogs API.
Actions: call POST /blogs/posts with title, content, slug and metadata; optionally update with PUT /blogs/posts/:postId.
POST /blogs/posts
title, content, slug, author, categories, status
Trigger: schedule events in Rankr lead to timed publishing via the Blogs API.
Actions: use POST /blogs/posts to create, GET /blogs/posts/url-slug-exists to verify slug, PUT /blogs/posts/:postId to update schedule.
POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists
title, content, slug, publishDate, status
Trigger: when new category or author is added in Rankr, sync with Blogs API.
Actions: fetch categories and authors using GET /blogs/categories and GET /blogs/authors to populate metadata.
GET /blogs/categories; GET /blogs/authors
categoryName; authorName; slug; bio
Automate publishing across platforms without writing code.
Streamline editorial workflows with centralized control from Rankr.
Get real time syncing and insights with minimal setup.
This glossary explains API terms and core processes for connecting the Blogs API with Rankr.
A specific URL that performs a defined action in the API.
Verification of identity to access API resources securely.
A URL friendly version of a post title used in the web address.
HTTP methods like GET, POST, PUT, DELETE used on endpoints.
Automatically publish drafts managed in Rankr to Blogs API when ready.
Share published posts to social platforms automatically.
Tag new posts with dynamic categories pulled from Rankr metadata.
Obtain API keys and authorize Rankr to access Blogs API.
Select endpoints like POST /blogs/posts and GET /blogs/categories to enable publishing.
Run tests to ensure data flows and deploy to production.
No code options are available via Rankr for common publishing tasks. Use the endpoints listed to automate posting. Build a workflow that pushes content from Rankr to Blogs API seamlessly. If you need help, consult the API docs and support resources.
Essential endpoints include POST /blogs/posts to create posts and GET /blogs/posts/url-slug-exists to verify slug. You may also use PUT /blogs/posts/:postId to update drafts and GET /blogs/categories and GET /blogs/authors for metadata.
The slug exists endpoint helps prevent duplicate URLs. Use GET /blogs/posts/url-slug-exists to check a slug before publishing. If it exists, adjust the title or slug.
Yes you can schedule posts using Rankr to set publishDate and status. Use POST /blogs/posts to create with a future date or PUT to update scheduling information.
API authentication uses keys or tokens and should be stored securely. Rotate credentials regularly and use restricted scopes. Enable HTTPS to protect data in transit.
Yes you can fetch authors and categories using GET /blogs/authors and GET /blogs/categories. This helps you assign authors and categorize posts in Rankr.
If data is missing, verify credentials, endpoints, and field mappings. Check response payloads and logs, and re-run the integration tests. Reach out to support if needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
