To authorize access to the Blogs API you will use an access token or API key with appropriate scopes and a secure connection.
Authenticate the Chorus by ZoomInfo app in GHL using a secure OAuth flow or API token provided by Chorus.
The endpoints below cover reading, creating and updating blog posts, schedules and author data.
Trigger on a new blog post draft created via POST /blogs/posts in Blogs API.
Actions push title, content, slug and metadata to Chorus to create a matching post.
POST /blogs/posts to create and then map to a Chorus post payload for publishing.
title, slug, content, author, category, publishedDate
Trigger on PUT /blogs/posts/:postId in Blogs API.
Actions push updated fields to Chorus and refresh publish time.
PUT /blogs/posts/:postId
postId, title, slug, content, status
Trigger on GET /blogs/categories and GET /blogs/authors to pull latest data.
Actions map category and author data into Chorus taxonomy and author records.
GET /blogs/categories and GET /blogs/authors
categories array, authors array, mapping fields
Automate publishing without writing code using bridges between the two apps.
Speed up editorial workflows with synchronized data and scheduling.
Maintain consistent metadata across channels and search engines.
This glossary explains core concepts used in this guide including API, endpoint, slug and OAuth.
API stands for Application Programming Interface and allows programs to interact.
An API endpoint is a specific URL that performs a function when called.
OAuth is a protocol for granting limited access without sharing user credentials.
A slug is a URL friendly version of a title used in web addresses.
Set up a trigger on new drafts to create a Chorus post and tag for review.
When a blog post is updated, push updates to Chorus to keep content aligned.
Check GET /blogs/posts/url-slug-exists before creating a new post to avoid duplicates.
Obtain tokens and set required scopes for both services.
Define which fields map to Chorus post data like title, content, slug and publish date.
Run end to end tests and set up alerts for failures.
No code is required to begin. Use the built in maps and triggers to connect Blogs API with Chorus by ZoomInfo and publish posts without writing code. Start with creating a blog post in Blogs API and map the payload to Chorus for posting.
To publish a post you typically use POST /blogs/posts in Blogs API and then map the fields to a Chorus post. Ensure the payload includes title, slug and content so Chorus can render the post correctly.
Use GET /blogs/posts/url-slug-exists to check if a slug already exists. If it does, generate a new slug or update the existing post accordingly.
Yes you can schedule posts by using the publish date field in the Blogs API payload and syncing it to Chorus. Use the scheduling workflow in Chorus or the corresponding API fields to time publishes.
The recommended method is OAuth 2.0 for secure access. API keys can also be used if provided by the service and configured securely.
Authors and categories are retrieved via GET /blogs/authors and GET /blogs/categories. Map these to Chorus authors and taxonomy so editors can select and assign correctly.
Error logs appear in the API dashboard and in Chorus connection logs. Enable webhooks if available and review failure messages and timestamps to troubleshoot quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
