Obtain an API key or OAuth token from the GHL developer console with the scope emails/builder.readonly to access and manage blog content from Mayar.
In Mayar, paste your client credentials and test the connection to ensure secure communication between Mayar and Blogs API.
Endoints include: GET emails/builder, GET emails/builder.write, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, emails/schedule.readonly, GET emails/schedule, blogs/post.write, POST /blogs/posts, blogs/post-update.write, PUT /blogs/posts/:postId, blogs/check-slug.readonly, GET /blogs/posts/url-slug-exists, blogs/category.readonly, GET /blogs/categories, blogs/author.readonly, GET /blogs/authors. Other related calls in this integration cover reading, writing, and updating blog content, as well as managing schedules and categories.
Trigger: when a new blog idea is available in Mayar, call POST /blogs/posts to create a draft.
Actions: pass title, content, slug, and author fields; set status to draft or ready for review.
POST /blogs/posts
Key fields: title, content, slug, authorId, status
Trigger: schedule posts for future publication from Mayar using a publishDate.
Actions: set publishDate, timezone, and status; use POST /blogs/posts to create or PUT /blogs/posts/:postId to update existing posts.
PUT /blogs/posts/:postId
Key fields: postId, publishDate, status
Trigger: fetch latest posts, authors, and categories to mirror in Mayar using GET /blogs/authors and GET /blogs/categories.
Actions: pull content and cache for display in Mayar; keep in sync with source data.
GET /blogs/authors
Key fields: authorId, name, bio
Automate blog creation and scheduling without writing code.
Keep blog content in sync across Mayar and your channels.
Use triggers and actions to streamline editorial workflows.
A quick glossary of elements and processes used to integrate Blogs API with Mayar, including endpoints, triggers, actions, method paths, and key fields.
A specific URL path that performs a function in the API, such as creating a post or listing authors.
An event in Mayar that starts a workflow, such as a new idea or a scheduled time.
An operation that runs in response to a trigger, like POST /blogs/posts or PUT /blogs/posts/:postId.
A URL-friendly identifier used in blog post URLs.
When a new blog idea is captured in Mayar, automatically draft a post in Blogs API using POST /blogs/posts with title and content.
Set a recurring schedule in Mayar to publish weekly summaries by hitting POST /blogs/posts with prepared content.
Sync edited content from your CMS back to Blogs API via PUT /blogs/posts/:postId to keep posts current.
In GHL, create an API credential for the Blogs API and note the client ID and secret; assign the scope ’emails/builder.readonly’ as required.
Enter the credentials into Mayar, select the Blogs API integration, and test the connection.
Create a trigger in Mayar (e.g., new idea) to call POST /blogs/posts and publish or draft posts automatically.
The Blogs API integration with Mayar enables automation of blog publishing and management without heavy coding. You can draft posts from Mayar ideas, publish on a schedule, and update existing content via secure API calls. This integration centralizes content workflows between Mayar and Blogs API for faster editorial cycles. The setup uses well-defined endpoints and triggers to minimize manual steps.
For posting and updating blogs, you will primarily use POST /blogs/posts to create posts and PUT /blogs/posts/:postId to update existing posts. Other helpful endpoints include GET /blogs/posts/url-slug-exists to verify slugs and GET /blogs/authors to fetch author details. You can also retrieve categories via GET /blogs/categories as part of content organization.
No advanced coding is required to start. The system supports no-code triggers and actions within Mayar that call the Blog API endpoints. Developers can customize fields later if needed, but the out-of-the-box setup works with drag-and-drop workflows.
Test the connection from Mayar by validating the API credentials and performing a simple POST to create a draft, then fetch the response. Check the returned status codes to confirm authentication and permissions. Ensure the scope matches what you intend to do (read/write permissions as needed).
Yes. You can schedule posts in advance by setting a publishDate and status in Mayar and using PUT /blogs/posts/:postId to adjust as needed. Scheduling enables a consistent publishing calendar across your channels.
Benefits include automated content creation, consistent publishing, and streamlined workflows between Mayar and Blogs API. The no-code setup reduces manual overhead and accelerates editorial cycles while preserving control over post metadata like titles, slugs, and authors.
Documentation for the Blogs API integration is available in both the GHL developer docs and the Mayar integration guides. Look for sections describing endpoints, triggers, actions, and credential setup to maximize your automation. If you need more, reach out to support for tailored guidance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
