Skip to main content
The Blog pillar is a full content engine — not a header-and-body table. Posts have categories and tags, scheduling, multi-language translations, featured images, SEO meta, and a research → write → image → translate → publish pipeline that runs as one async job.

What this gives you

  • Posts with draft, scheduled, published, archived lifecycle.
  • Translations per language with their own title, content, excerpt, and SEO meta.
  • Categories and tags with slugs, attached many-to-many.
  • Scheduling — set scheduled_at and we publish at the precise minute.
  • AI authoring pipeline — one POST kicks off topic research, writing, image generation, translation to every target language, and SEO meta.

Quick example

Create a published post in English, then async-translate it into French:

Common workflows

1. Generate a multi-language post end to end

The headline workflow. One POST kicks off the full pipeline (research → outline → write → featured-image → SEO meta → per-language translations) and returns a Job reference. Subscribe to blog_post.published for the finished result, or poll.
SDK
cURL
Cost: 60 credits for the post itself (blog_post — covers research, draft, and featured image). Per-language translations charge 7 credits each (translate_language) on top, billed when each language lands.

2. Schedule a post for next Tuesday

SDK
cURL
The post enters scheduled state. At the exact minute we transition it to published and fire the blog_post.published webhook.

3. Edit and republish

Patch a published post in-place. Text fields (title, content, excerpt, meta_title, meta_description) write to the translation row resolved by language_code (default en); post-level fields (slug, status, category_id, featured_image) write to the post itself.
SDK
cURL

4. Translate an existing post into a new language

SDK
Cost: 7 credits per language (translate_language).

5. Lifecycle helpers

SDK

Reference