Authenticate securely with the Blogs API using your API key or OAuth credentials. Keep credentials safe and grant only the required scope to limit access to blog and related data.
Connect Smokeball by generating a secure auth token, validating the connection with a test post, and enabling automated workflows to run smoothly.
Core endpoints include: GET emails/builder; 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
Trigger: When a new blog draft is created in Smokeball
Actions: POST /blogs/posts to publish the draft; include title, content, slug, and metadata
POST /blogs/posts
Key fields: title, content, slug, excerpt, publishDate
Trigger: Smokeball post updated
Actions: PUT /blogs/posts/:postId to apply edits
PUT /blogs/posts/:postId
Key fields: postId, title, content, slug
Trigger: Before publishing, verify slug uniqueness
Actions: GET /blogs/posts/url-slug-exists to check slug
GET /blogs/posts/url-slug-exists
Key fields: slug
Streamlined content workflow with zero code
Faster publishing and updates across your blog and Smokeball data
Centralized content management and audit trail
A quick glossary of terms used in this guide: triggers, actions, endpoints, and fields.
An event that starts an automation, such as a new Smokeball draft.
An operation performed in response to a trigger, such as posting to the Blogs API.
A specific URL in the API that performs a function like creating or fetching posts.
A URL-friendly version of a post title used to identify posts uniquely.
Automatically generate blog drafts from Smokeball task templates and publish via the Blogs API.
Schedule posts to publish at optimal times across channels via the Blogs API.
Implement automatic retries and alerting in Smokeball when API calls fail.
Create an API key or OAuth credentials for Blogs API and securely store them in Smokeball.
Enter credentials and test the connection with a sample post.
Create a workflow that creates and updates blog posts using the endpoints listed above.
Smokeball connects to the Blogs API using OAuth or API keys, then uses a mapped workflow to trigger actions when new drafts are created. This setup lets you push content from Smokeball into the Blogs API without manual steps. The integration is designed to be user-friendly and to minimize coding.
For publishing posts you typically use POST /blogs/posts to create posts and PUT /blogs/posts/:postId to update them. You can also verify slug availability with GET /blogs/posts/url-slug-exists to avoid duplicates. These endpoints cover core publish and update flows.
No advanced coding is required if you use the available templates and the Zapier-style workflow builder within Smokeball. You’ll configure credentials, map fields, and enable automated actions with guided steps.
Yes. Updates flow from Smokeball to Blogs API can incrementally modify titles, content, and metadata via PUT /blogs/posts/:postId. You can trigger edits whenever a Smokeball draft changes.
Slug checks are available via GET /blogs/posts/url-slug-exists. Run a pre-publish check to confirm the slug is unique, then proceed with POST to create the new post.
Authentication is handled through secure tokens or keys. Use the least-privilege scope necessary for your workflow and rotate credentials regularly to maintain security.
Logs and errors appear in Smokeball’s integration dashboard and the connected API provider’s console. Use those logs to troubleshoot failed requests and verify successful data Sync.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
