To connect Blogs API, authenticate using OAuth 2.0 with the scope: emails/builder.readonly. You’ll create a connected app in GHL and securely store the access token for API calls.
TrueReview authenticates to GHL via the standard OAuth 2.0 flow. After authorization, TrueReview receives tokens to access the Blogs API endpoints listed below.
Use endpoints such as GET /blogs/categories, GET /blogs/authors, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId to manage content and metadata. These endpoints enable post creation, updates, slug validation, and taxonomy lookups for a complete publishing workflow.
Trigger: A finalized article in TrueReview initiates a POST to /blogs/posts to create a new blog entry.
Actions: Map title, content, slug, categoryId, and authorId; optionally set published status and scheduling.
Method Path: POST /blogs/posts
Key fields: title, content, slug, categoryId, authorId, publishedAt
Trigger: Updates in TrueReview map to PUT /blogs/posts/:postId to refresh published content.
Actions: Update title, content, slug, categoryId, and authorId; ensure slug integrity and publishing state.
Method Path: PUT /blogs/posts/:postId
Key fields: postId, title, content, slug, categoryId, authorId
Trigger: Before creating a post, verify slug availability with GET /blogs/posts/url-slug-exists.
Actions: Validate slug uniqueness, then proceed with POST /blogs/posts; handle conflicts gracefully.
Method Path: GET /blogs/posts/url-slug-exists
Key fields: slug
No-code setup lets marketers automate publishing without writing a line of code, using visual builders and API mappings.
A centralized workflow between TrueReview and the Blogs API reduces manual data entry and minimizes errors across publishing, categorization, and author assignment.
Rapid testing and deployment are supported with API endpoints and test data, enabling faster go-to-market for new content strategies.
This glossary defines common terms you’ll encounter when connecting TrueReview with the Blogs API: endpoints, slug, authentication, triggers, and actions, with practical mapping guidance for this integration.
A specific URL in the API that performs a defined action (e.g., creating or updating a blog post).
A URL-friendly string derived from the post title used to identify the post in the URL.
An authorization framework that allows apps to obtain limited access tokens to call the API on behalf of a user.
The human-readable title of a blog post used for display and SEO purposes.
Pull top TrueReview articles and auto-create summary blog posts in Blogs API to fuel weekly site content without manual drafting.
Draft in TrueReview, then push revisions via PUT /blogs/posts/:postId, keeping a clean version history and consistent metadata.
Generate SEO-friendly titles and slugs from TrueReview insights to optimize search rankings and click-through rate.
Create OAuth credentials in GHL for the Blogs API and authorize TrueReview to access the required scopes.
In TrueReview, map actions to POST, PUT, and GET endpoints such as /blogs/posts, /blogs/posts/:postId, and /blogs/posts/url-slug-exists.
Define required fields (title, content, slug, categoryId, authorId) and run end-to-end tests to verify the flow from creation to publication.
You can manage blog posts using endpoints like POST /blogs/posts to create new posts and PUT /blogs/posts/:postId to update existing ones. These calls let you set title, content, slug, categoryId, and authorId during creation or updates. Additionally, GET /blogs/posts/url-slug-exists helps you avoid duplicate slugs before publishing.
Yes. You can update published posts using PUT /blogs/posts/:postId. This allows you to correct content, adjust metadata, or update categories and authors after initial publication. Ensure postId is included and your changes align with your publishing schedule.
Slug existence can be checked with GET /blogs/posts/url-slug-exists before creating a post. This reduces slug collisions and preserves clean URLs for SEO. If a slug exists, you can alter the slug or generate an alternative version prior to posting.
Authentication uses OAuth 2.0 with the scope emails/builder.readonly as configured for this integration. You’ll grant TrueReview access via the connected app in GHL and securely manage tokens. Tokens should be stored securely and rotated as needed to maintain a secure connection.
No-code options are available. You can connect TrueReview to the Blogs API using visual builders and API mappings, avoiding custom code while still enabling automation. Leverage the predefined endpoints and field mappings to accelerate setup.
The setup requires the emails/builder.readonly scope (as noted) and any additional scopes needed by your specific workflow. Ensure all endpoints you plan to use are granted access in the OAuth configuration. Review permissions with your security or admin team before going live.
Test the integration in a staging environment by creating draft posts, performing updates, and validating slug checks. Use sample data to verify end-to-end publishing and error handling. Monitor API responses and adjust field mappings as needed for reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
