Authenticate securely with the Blogs API using API keys or OAuth tokens, then connect to Bmby to enable authorized requests for posts, categories, and authors.
Bmby uses a secure connection to the Blogs API, passing your API credentials and access tokens to perform create, read, update, and delete operations on blog data.
Key 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: A new draft post is ready in Bmby.
Actions: create a post via POST /blogs/posts, generate a slug with a slug-check, and publish.
Method/Path: POST /blogs/posts
Key fields: title, content, author, category, slug, status
Trigger: Post details updated in Bmby.
Actions: update post via PUT /blogs/posts/:postId; refresh metadata as needed.
Method/Path: PUT /blogs/posts/:postId
Key fields: postId, title, content, tags, status
Trigger: Content planning session in Bmby.
Actions: fetch authors via GET /blogs/authors, fetch categories via GET /blogs/categories, and validate slug via GET /blogs/posts/url-slug-exists.
Method/Path: GET /blogs/authors and GET /blogs/categories and GET /blogs/posts/url-slug-exists
Key fields: authorId, categoryId, slug
No-code automation: publish, update, and manage blog content without writing code.
Centralized content workflow: manage emails, schedules, and blogs from one dashboard.
Secure, scalable access with API keys and OAuth tokens, no server tweaks required.
Key terms and processes you’ll encounter when connecting Blogs API with Bmby.
A defined set of rules that enables two systems to communicate and exchange data.
A URL-friendly identifier used in blog post URLs and SEO.
A blog article created, updated, and published via the Blogs API.
A specific path on an API that performs an action or returns data.
Set up a weekly automation that aggregates your posts in Bmby and publishes to Blogs API.
Whenever an author profile updates in Bmby, sync author data to Blogs API.
Check slug existence prior to publish to avoid duplicates.
Obtain API keys, OAuth tokens, and set up allowed scopes, then prepare endpoints for posts, authors, and categories.
Authenticate in Bmby to gain access to Blogs API and authorize data flow.
Run a test by creating a draft post in Bmby and publishing to Blogs API using the core endpoints.
No-code setup is all you need. Use Bmby’s visual workflow builder to connect the Blogs API endpoints and map fields, then test publishing straight to your blog site. If you need more control, you can apply API credentials and optional webhooks for custom flows. Tip: start with a simple post publish to validate the connection before enabling automation across categories and authors.
To publish a post you’ll typically use POST /blogs/posts and ensure required fields (title, content, slug, author, and category) are provided. You may also use blogs/post.write for content draft operations and blogs/post-update.write for updates. After creation, verify slug existence with GET /blogs/posts/url-slug-exists to avoid duplicates.
Yes. Use PUT /blogs/posts/:postId to update title, content, or metadata. If you need to change a slug, update it in the payload and revalidate with the slug-check endpoint. Remember to re-publish if your workflow requires live updates on the site.
Use GET /blogs/posts/url-slug-exists to confirm slug availability prior to publishing. This helps prevent duplicate URLs in your blog feed. If a slug already exists, adjust the slug text or slugify a new variation and retry.
Author and category data are retrieved via GET /blogs/authors and GET /blogs/categories. Map the IDs or slugs to your Bmby fields so posts can be properly categorized and attributed. Keep author and category data in sync with your source of truth to avoid orphaned references.
Usage limits depend on your API plan. Monitor call counts and implement batching or caching where possible to stay within quotas. If you hit limits, consider requesting higher quotas or spreading requests across intervals in your automation workflows.
Use secure storage for API keys, rotate credentials periodically, and prefer OAuth where available. Use webhooks and IP whitelisting if supported by your environment to enhance security. Always follow your organization’s security policies when handling credentials.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
