API documentation

Use this reference to integrate website analysis, streaming job updates, and content generation with Automate My Blog. Paths below match the production/staging Node API router.

Authentication required for almost all write paths

There is no separate public API key for third-party integrators in this table. Treat every /api/v1 route except /health and /api/v1/public-site/:username as requiring the same auth model as the web app unless your deployment explicitly documents otherwise.

Try the product flow

See platform features

Core endpoints

Method	Endpoint	Purpose	Auth
GET	`/health`	Liveness probe on the API host (same deployment as /api/v1/*)	Public
GET	`/api/v1/public-site/:publicUsername`	Read published hosted landing HTML + theme (no auth when hosting is enabled)	Public
POST	`/api/v1/jobs/website-analysis`	Enqueue async website analysis (returns jobId)	Session, JWT, or x-session-id
GET	`/api/v1/jobs/:jobId/status`	Poll job status and result payload when terminal	Session, JWT, or x-session-id
GET	`/api/v1/jobs/:jobId/narrative-stream`	Server-sent events for analysis narration / progress	Session, JWT, or x-session-id
POST	`/api/v1/jobs/content-generation`	Enqueue async enhanced blog generation (worker + credits)	Session, JWT, or x-session-id
POST	`/api/v1/topics`	Generate topic suggestions for a selected audience	Session optional (see backend optionalAuth)
POST	`/api/v1/enhanced-blog-generation/generate`	Synchronous enhanced blog generation (credits; long-running)	Session or JWT

Webhook events

Product webhooks (content.ready / publish.completed style) are not a separate public contract today.
Prefer jobs + status + narrative-stream / stream for durable integration; confirm any webhook program with support before building to these names.

Integration guide

1. Authenticate (HttpOnly session cookie after login, or Authorization: Bearer …; some job routes also accept x-session-id).
2. POST /api/v1/jobs/website-analysis with { url } → jobId; poll GET /api/v1/jobs/:jobId/status until succeeded or failed.
3. Optionally open GET /api/v1/jobs/:jobId/narrative-stream (SSE) for streaming narration while the job runs.
4. For topics, POST /api/v1/topics with audience + organization context as used in the dashboard.
5. For posts, choose POST /api/v1/jobs/content-generation (async) or POST /api/v1/enhanced-blog-generation/generate (sync); both require credits and auth.

Machine-readable specs

An OpenAPI bundle is not guaranteed on every deployment. For a contract-level audit, diff this table against register-api-routes.js in the backend repo and run smoke curl calls against your target REACT_APP_API_URL.

Explore:

Features

Pricing

Why Not ChatGPT

Client Growth Playbook

API Docs