Authenticate requests to the Blogs API using your API key or OAuth credentials and restrict access to the emails and blogs endpoints you use with VoIPstudio.
Configure VoIPstudio to securely store the Blogs API credentials and sign requests when calling endpoints from within workflows.
Use the endpoints below to read and write emails, manage blog posts, and verify URL slugs. Not every endpoint is required for every workflow.
Trigger: retrieving existing email templates when composing newsletters.
Actions: read templates, populate the composer, and allow edits.
Method and path: GET /emails/builder
Key fields: locationId, templateId, subject, body
Trigger: create a new blog post when ideas are ready.
Actions: publish, assign author, set slug and metadata
Method and path: POST /blogs/posts
Key fields: postId, title, slug, content, status
Trigger: update a post after review
Method and path: PUT /blogs/posts/:postId
Key fields: postId, title, content, status
Automate workflows without writing code.
Sync emails and blog posts across channels in minutes.
Unify data flows for faster campaigns and clearer insights.
A quick glossary of terms and processes used in this integration guide.
Application Programming Interface that allows apps to talk to each other.
A URL-friendly unique identifier for a blog post.
A callback mechanism that notifies your systems about events in real time.
Open Authorization protocol for secure access to APIs.
Convert incoming emails into blog post drafts in Blogs API.
Publish concise recaps to your email templates for newsletters.
Automatically post snippets to social channels once a post goes live.
Obtain API keys from Blogs API and safely save them in VoIPstudio.
Connect endpoints such as GET /emails/builder and POST /blogs/posts, and assign scopes.
Run tests, validate responses, and refine automations.
Answer paragraph 1. You can authenticate by including your API key or OAuth token in the request header. Ensure the credentials have access to emails/builder and blogs endpoints. Answer paragraph 2. Use secure storage and rotate credentials periodically to maintain security.
Answer paragraph 1. For newsletters, use GET /emails/builder to pull templates and POST /blogs/posts to create new content. Answer paragraph 2. Use PUT /blogs/posts/:postId to update drafts before publishing.
Answer paragraph 1. Yes, you can update content via PUT /blogs/posts/:postId. Answer paragraph 2. Ensure you handle slug updates and titles consistently.
Answer paragraph 1. Use GET /blogs/posts/url-slug-exists to verify slug availability. Answer paragraph 2. If exists, modify slug or title before publishing.
Answer paragraph 1. Use GET /blogs/authors to fetch author data. Answer paragraph 2. For categories, use GET /blogs/categories or GET /blogs/categories to list.
Answer paragraph 1. Be mindful of rate limits and implement exponential backoff. Answer paragraph 2. Cache responses where possible and batch requests when appropriate.
Answer paragraph 1. Implement retries with backoff and handle 429 or 5xx responses gracefully. Answer paragraph 2. Log failures and alert your team when thresholds are exceeded.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
