Content Pipeline Overview for Developers
Understand how ScaleBlogger's content pipeline works — from idea discovery to publishing — and how to integrate with it via the API.
Content Pipeline Overview for Developers
Audience: Developers and AI agents integrating with or building on top of ScaleBlogger
How the Content Pipeline Works
ScaleBlogger's content pipeline automates the journey from idea to published article. Understanding the pipeline helps you build integrations that respond to content lifecycle events and extend the platform's capabilities.
Pipeline Stages
Every piece of content moves through these stages:
| Stage | What Happens | Developer Touchpoints |
|---|---|---|
| 1. Idea Discovery | AI identifies content opportunities based on your website, niche, and competitors | Ideas appear in the dashboard and can be created via the API |
| 2. Brief Generation | Ideas are expanded into structured content briefs with target keywords, audience, and outline | Briefs can be generated or provided via API |
| 3. Article Writing | AI generates a full article from the brief, including SEO optimization and internal linking | Track progress via processing_status on the article draft |
| 4. Quality Review | Articles are scored for quality, SEO, and brand alignment before publishing | Articles that need review are flagged with review_pending status |
| 5. Publishing | Approved articles are formatted and published to your connected CMS | Use webhooks or poll the API to detect newly published content |
Content Statuses
Track where your content is in the pipeline using these status values:
| Status | Meaning |
|---|---|
draft | Article is being written or has been generated |
ready_for_review | Writing complete, pending quality check |
review_pending | Held for manual review before publishing |
approved | Passed review, ready to be scheduled |
scheduled | Queued for publishing at a specific date/time |
published | Live on your CMS |
failed | An error occurred (can be retried) |
Working with the Pipeline via API
Generating a Content Brief
POST /api/briefs/generate
Authorization: Bearer <your-token>
Content-Type: application/json
{
"website_id": "your-website-id",
"topic": "How to optimize images for web performance",
"target_keywords": ["image optimization", "web performance"]
}
Checking Article Status
GET /api/articles/:draft_id
Authorization: Bearer <your-token>
The response includes status, processing_status, and published_url (when available).
Publishing an Article
POST /api/articles/publish
Authorization: Bearer <your-token>
Content-Type: application/json
{
"draft_id": "your-draft-id"
}
Scheduling and Automation
ScaleBlogger supports fully automated content pipelines:
- Editorial Plans: Define how many articles per week and preferred publishing days/times
- Content Calendar: Articles are automatically scheduled based on your plan
- Auto-Publishing: When enabled, approved articles publish automatically at their scheduled time
CMS Integration
ScaleBlogger publishes directly to your CMS. Supported platforms:
- WordPress — via REST API (wp-json/wp/v2)
- Ghost — via Admin API
- Custom/Headless CMS — via a simple REST contract you implement (see Custom CMS Integration Guide)
Best Practices
- Review briefs before generation to ensure content aligns with your strategy
- Use the content calendar for consistent publishing cadence
- Monitor failed items and retry them promptly
- Set up your CMS connection before enabling auto-publishing
- Use webhooks to trigger downstream workflows when articles are published
Related Resources
- Custom CMS Integration Guide — Build a custom publishing endpoint
- Understanding the Content Pipeline — Non-technical overview