Use OAuth 2.0 with Azure AD to authorize the Blogs API. Request the scope emails/builder.readonly to read builder data and additional scopes as needed for writing.
Rankr authenticates via OAuth 2.0 with Azure AD to obtain access tokens for the Blogs API, enabling secure calls from your app.
Endpoint overview: GET emails/builder (read builder data); POST emails/builder (write to builder data); POST /emails/builder/data (submit builder data payload); DELETE /emails/builder/:locationId/:templateId (remove a template). Schedule: emails/schedule.readonly (read-only); GET emails/schedule (read schedule). Blog posts: blogs/post.write (write access); POST /blogs/posts (create post); PUT /blogs/posts/:postId (update post); POST /blogs/post-update.write (update post via dedicated endpoint). Slug check: blogs/check-slug.readonly; GET /blogs/posts/url-slug-exists (check slug existence). Categories: blogs/category.readonly; GET /blogs/categories. Authors: blogs/author.readonly; GET /blogs/authors.
Trigger events occur when a builder is created or a schedule item changes.
Actions: fetch builder data, fetch schedules, and refresh local cache.
Methods and paths: GET emails/builder, GET emails/schedule.
Key fields: locationId, scheduleId, templateId.
Trigger when a draft is ready to publish or an author edits a post.
Actions: create via POST /blogs/posts; update via PUT /blogs/posts/:postId; apply post updates via blogs/post-update.write.
Methods: POST /blogs/posts, PUT /blogs/posts/:postId, POST /blogs/post-update.write.
Key fields: postId, slug, title, content.
Trigger when categories or authors are updated.
Actions: fetch GET /blogs/categories and GET /blogs/authors and GET /blogs/posts/url-slug-exists to validate slug changes.
Methods: GET blogs/categories, GET /blogs/authors, GET /blogs/posts/url-slug-exists.
Key fields: categoryId, authorId, slug.
Automate integration without writing code.
Seamless data flow between GHL and Rankr via Azure AD.
Faster setup with pre-built endpoints and clear mappings.
Glossary of OAuth terms, API endpoints, scopes, and data mapping used in the Azure AD connection between GHL Blogs API and Rankr.
OAuth 2.0 is an authorization framework that lets applications access resources on behalf of a user or service, using access tokens.
An API endpoint is a URL path through which you can perform actions like reading or writing data.
Scopes define what parts of an API your token can access, such as readonly vs write access.
Azure AD is the identity provider used to secure access to GHL and your Rankr app, issuing tokens for API calls.
Automatically publish approved Rankr drafts to Blogs API when status changes to ready.
Schedule posts to go live at optimized times with authenticated requests.
Sync author details from Blogs API to Rankr to keep bios current.
Create an Azure AD app registration (client ID and secret), set redirect URIs, and configure permissions for Blogs API.
Add scopes such as emails/builder.readonly and others; authorize endpoints for reading and writing.
Use the Blogs API endpoints to test token acquisition and calls, verify data mapping.
GHL is the platform that exposes APIs your app can call to manage data and workflows. It provides secure access to resources via tokens. In this integration, the Blogs API on GHL is connected to Rankr through Azure AD, using OAuth 2.0 to obtain access tokens for API calls.
Azure Active Directory acts as the identity provider and authorization server. It issues tokens after the app is registered and consent is granted. This ensures that calls to the Blogs API are secured and auditable, with scopes controlling what is accessible.
Commonly requested scopes include emails/builder.readonly for viewing builder data and emails/builder.write for updates. Additional scopes may be added as needed. Always request the minimum scope required for the task and adjust as your app evolves.
Yes. The integration supports creating and updating blog posts via endpoints like POST /blogs/posts and PUT /blogs/posts/:postId. Use blogs/post-update.write for batch updates or automation flows as appropriate.
Test the integration by performing token retrieval from Azure AD and then calling the endpoints in a controlled environment. Validate responses, check data mappings, and verify that write operations have the expected effects.
Tokens expire and can be refreshed using the refresh token flow. If a token is revoked, you will need to re-authenticate the app in Azure AD. Implement error handling in your app to detect 401/403 responses and trigger a re-auth flow.
The endpoints list is provided in the Endpoint section of this page. It includes CRUD operations for emails, blogs, categories, and authors. Each endpoint is documented with its method, path, and required scope.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
