Authenticate every request with your API key and OAuth scopes to securely access the Blogs API from Zenvia workflows.
Use your Zenvia OAuth credentials or API tokens to authorize communications with the Blogs API, ensuring only approved apps can publish or fetch posts.
GET emails/builder; POST emails/builder; POST /emails/builder/data; GET emails/schedule; GET /blogs/posts; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts
When a new blog post is published in Blogs API, trigger a Zenvia message to subscribers.
Create a message template, map title and excerpt, deliver via SMS/WhatsApp.
POST /blogs/posts
title, content, slug, excerpt, publish_date
When a post is updated in Blogs API, notify via Zenvia.
Send update notification, requeue message if failed.
PUT /blogs/posts/:postId
postId, title, content
Schedule a post to publish at a future time and notify channels.
Set scheduled_time, confirm delivery windows.
POST /blogs/posts with scheduled_time
title, content, slug, scheduled_time
Zero-code automation for cross-channel blog updates.
Visual workflow setup with templates and triggers in Zenvia.
Scales with your content team as you publish more posts.
This section defines core terms: endpoints, authentication, triggers, and data fields used to connect Blogs API with Zenvia.
Application Programming Interface — a collection of endpoints and methods to interact with Blogs API from Zenvia.
A URL-friendly identifier for a post, used in routing and SEO.
OAuth tokens authorize secure access between Zenvia and Blogs API.
A specific URL path to perform an action in the API.
Publish a blog post and automatically push personalized messages via SMS/WhatsApp to subscribers.
Schedule posts and coordinate with a drip campaign to nurture readers.
Automatically update subscribers when a post changes status, increasing engagement.
Create API credentials for Blogs API and authorize Zenvia to access them.
Define triggers like new_post and post_updated, map to actions in Zenvia.
Run tests, monitor results, promote to production.
The Blogs API provides programmatic access to create, edit, and publish blog content. When connected to Zenvia, you can trigger messages or campaigns from new posts. This integration enables automated multi-channel publishing and ensures your audience receives timely updates via SMS or WhatsApp.
To publish a post, use POST /blogs/posts to create the entry. You can verify a slug with GET /blogs/posts/url-slug-exists. In a Zenvia workflow, map these endpoints to triggers and direct the results to your chosen channel for notifications.
Authentication uses API keys and OAuth tokens. Ensure your Blogs API credentials have read/write scopes for posts. Store tokens securely and rotate them regularly within Zenvia.
Yes. You can schedule posts by including a scheduled_time parameter with POST /blogs/posts. Zenvia can queue notifications for future delivery and fire them when the post goes live.
Zenvia supports SMS and WhatsApp channels for blog updates. You can tailor messages per recipient and channel using templates and dynamic fields.
Key fields include title, content, slug, excerpt, categories, author, and scheduled_time. These ensure accurate publishing and proper routing of notifications.
The endpoint list is documented under the Blogs API section of the docs. Look for posts, slug checks, and category endpoints to understand available actions. You can also reference related endpoints like emails and authors to support broader workflows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
