Use OAuth 2.0 with your Bloom app to securely authorize access to blog endpoints such as GET emails/builder, POST /blogs/posts, and PUT /blogs/posts/:postId.
To authorize Bloom to use the Blogs API, create an OAuth client in Bloom, configure redirect URIs, and grant the blogs read/write scope to enable posting and updates.
– GET emails/builder (read emails builder) – POST emails/builder (write emails builder) – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – emails/schedule.readonly (read-only access) – GET emails/schedule – POST /blogs/posts – POST /blogs/posts – PUT /blogs/posts/:postId – 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 post is published in Bloom, pull post data via POST /blogs/posts to create the corresponding entry.
Actions: POST /blogs/posts to create the blog, then optionally notify subscribers via Bloom’s email builder.
POST /blogs/posts
title, content, slug, category, author
Trigger: Blog post updated in source; Bloom post should reflect changes.
Actions: PUT /blogs/posts/:postId to update title, slug, and content; propagate category and author changes.
PUT /blogs/posts/:postId
postId, title, content, slug, category, author
Trigger: Slug verification before publishing to ensure unique URLs.
Actions: GET /blogs/posts/url-slug-exists to check slug; then POST /blogs/posts to publish; use GET /blogs/categories for taxonomy.
GET /blogs/posts/url-slug-exists
slug, postId (optional), exists
Automate publishing workflows without writing code, reducing manual steps.
Keep content consistent across Bloom and your blog platform with synced updates.
Improve SEO and audience reach with timely, accurate post metadata and slugs.
A quick glossary of terms used in this guide to help you understand API endpoints, authentication, and data fields.
A specific URL that performs a defined action in a web service, for example GET /blogs/authors returns a list of authors.
OAuth 2.0 is a framework for delegating access to user data without sharing passwords.
A URL-friendly version of a post title used in the post URL.
A callback URL that receives real-time notifications when an event happens in a service.
When a new post is published in the source blog, automatically generate a Bloom draft with the title and excerpt.
Sync title, slug, and content edits back to Bloom to keep campaigns aligned.
Trigger Bloom campaigns or emails when posts go live using the schedule endpoints.
Create OAuth credentials in Bloom, authorize the Blogs API with read/write access.
Enable endpoints like POST /blogs/posts, PUT /blogs/posts/:postId, and GET /blogs/authors in Bloom.
Create triggers and actions to automate publishing, updates, and promotion.
No coding is required to get started. Use Bloom’s built-in automation to connect to the Blogs API with ready-made actions and triggers. For advanced flows, you can customize webhooks or use the API endpoints directly. Start with simple POST and PUT operations to create and update posts.
Begin with creating a post (POST /blogs/posts) and then update (PUT /blogs/posts/:postId) as edits happen. Also ensure you can check slug existence (GET /blogs/posts/url-slug-exists) to prevent conflicts.
Test the connection by authenticating, then triggering a sample POST to /blogs/posts and confirming the post appears in Bloom. Use the slug check to validate that URLs don’t collide.
Scopes like read/write are required for endpoints such as GET /blogs/authors and POST /blogs/posts. Treat tokens securely and rotate credentials per your security policy.
Yes. Use PUT /blogs/posts/:postId to update title, content, slug, and metadata after publishing. Bloom will reflect these changes in corresponding campaigns or automations.
Review the endpoint list in the Bloom integration docs, or consult the Blogs API reference for details on each endpoint’s parameters and response structure.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
