To disconnect, revoke the Blogs API access token or API key from Rankr and remove any stored credentials, ensuring no active scopes remain.
In Rankr, delete the saved connection credentials for Blogs API and confirm changes to prevent accidental re‑connection.
Endpoints touched in this integration include: GET emails/builder; POST emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; GET blogs/categories; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/authors; GET /blogs/categories; GET /blogs/posts; GET /blogs/posts/url-slug-exists.
Trigger: a new draft in Rankr prompts creation of a blog post via Blogs API.
Actions: fetch draft content, POST to /blogs/posts, and set slug/title accordingly.
Method path: POST /blogs/posts to create, PUT /blogs/posts/:postId to update.
Key fields: title, content, author, publishDate, slug
Trigger: schedule job to publish posts at predefined times
Actions: verify slug via GET /blogs/posts/url-slug-exists, then POST /blogs/posts at the scheduled time
Method path: POST /blogs/posts; PUT /blogs/posts/:postId
Key fields: postId, slug, publishDate, status
Trigger: performance signals from Rankr guide content tweaks
Actions: fetch post performance metrics and update posts via PUT /blogs/posts/:postId
Method path: PUT /blogs/posts/:postId
Key fields: postId, views, engagement, updatedAt
No‑code setup lets you disconnect and reconfigure integrations quickly without writing code.
Automations can be modified with clicks, presets, and simple toggles.
Auditable changes and rollback options help maintain data integrity after disconnecting.
This glossary defines terms like API, endpoint, authorization, and slug, and describes the steps for safely disconnecting the Blogs API from Rankr.
Application Programming Interface: a set of rules and tools that enable software components to communicate.
The process of granting permission to access specific resources and operations.
A defined URL path that exposes a function of a service to be called by a client.
A URL-friendly string derived from a post title used in the blog URL.
When a new client brief arrives, trigger a draft blog post via the Blogs API to kick off content creation in Rankr.
Schedule posts to publish automatically at set times using Rankr workflows.
Adjust future posts based on performance data from Blogs API and Rankr analytics.
Create or retrieve API credentials for Blogs API and securely store them in Rankr.
Select and test the endpoints you will use (blogs, emails, categories) within Rankr.
Run tests, verify data flow, and set up alerts for failures.
You can revoke access from the Rankr settings by navigating to Connected Apps > Blogs API and selecting Revoke. This will invalidate the token and prevent further calls. After revoking, you should re-check any workflows that may still reference the old credentials to avoid errors. Two steps: revoke the token and remove stored credentials. If your system uses OAuth, you may need to re-authenticate later.
No coding required: you can disconnect using the UI. The platform stores the connection state and credentials; removing them stops automatic calls. If you need to reconnect, you can re-run the OAuth or API key setup.
After disconnect, calls to endpoints will fail until you re-connect. It’s safe to leave data in place; you may want to archive logs. Avoid continuing to issue updates to endpoints that expect an active connection until re-authenticated.
Scheduled posts will not publish after disconnect if the job was tied to the connection. You can export drafts and re-create schedules after reconnecting.
Yes. You can re-connect later by re-authorizing in Rankr and selecting the Blogs API scopes again. Existing data remains in Rankr; you may need to re-establish webhooks.
Disconnecting does not erase content already stored in Rankr; it only stops active calls to Blogs API. Data remains accessible through Rankr unless you delete it.
API docs for Blogs API are hosted in the Rankr docs section under Connected Apps. If you can’t locate it, contact support for the precise doc URL and endpoint details.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
