Authenticate requests to Blogs API with your unique API key and access token. Set the scope to include emails/builder and blogs endpoints as needed. Store credentials securely in CentrixOne and refresh tokens automatically where supported.
CentrixOne securely stores your API credentials and uses tokens to connect to Blogs API. Ensure you grant the required scopes and test connectivity using the built-in connection tester.
Core endpoints include: GET emails/builder; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; POST /blogs/post-update.write; GET blogs/categories; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts; GET /blogs/check-slug.readonly.
Trigger when a new blog post is published to automatically populate email templates.
Actions: fetch builder templates, create/update emails, and schedule send times.
Methods: GET emails/builder; POST emails/builder; POST /emails/builder/data.
Key fields: templateId, locationId, content, subject.
Trigger: when a post is created or updated, push to CentrixOne workflows.
Actions: create/update posts, check slug, and publish to channels.
Methods: POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists.
Key fields: postId, slug, title, content.
Trigger: schedule read-only endpoints to orchestrate campaigns.
Actions: schedule GET /emails/schedule and manage categories/authors.
Methods: GET emails/schedule; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts/url-slug-exists.
Key fields: scheduleId, categoryId, authorId, slug.
Automate content-to-campaign workflows without writing a line of code.
Centralize content planning, publishing, and marketing in one place.
Ship consistent messaging faster with reusable templates and post automation.
Key elements include API endpoints, authentication, triggers, actions, and data fields used to connect Blogs API with CentrixOne.
A unique credential used to authenticate requests to Blogs API.
A specific URL path in the API that performs a function, such as retrieving posts or creating a new draft.
A URL-friendly identifier for a blog post used in routing and SEO.
A callback URL that triggers actions when an event occurs (e.g., new post published).
Pull latest posts and generate concise email-ready summaries to populate templates.
Use the authors endpoint to tailor messages by writer and audience.
Coordinate blog publication with email and social posts on a schedule.
Obtain your Blogs API key and configure the required scopes in CentrixOne.
Use sample requests to verify endpoints and ensure data flows between systems.
Create automations that pull posts, populate templates, and schedule sends.
The Blogs API is a suite of endpoints that lets you create, read, update, and publish blog content, and manage email templates. It is designed to work with CentrixOne to streamline content-to-campaign workflows. Use the available endpoints to fetch templates, create posts, schedule deliveries, and verify slug existence.
To authenticate, use your API key and, if supported, an access token. Set the appropriate scopes (for example, emails/builder.readonly) to access blog templates and scheduling data. Store credentials securely in CentrixOne.
Available endpoints cover email templates, blog posts, categories, authors, and scheduling. For example GET emails/builder, POST /blogs/posts, GET /blogs/posts/url-slug-exists, and GET /blogs/categories.
Yes. You can automate posting and email campaigns by triggering on new blog posts or scheduled times. Use CentrixOne workflows to publish posts and send email updates automatically.
No heavy coding is required. The pre-built endpoints and CentrixOne’s visual workflow builder let you connect apps with drag-and-drop actions.
Common scopes include emails/builder.readonly for reading templates and blogs/post-write for posting content. Always request the minimum scope necessary.
Test the connection using a sandbox or staging environment, verify data flowing between blogs and emails, and monitor automation logs.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
