API Overview
HTTP API for drafting and publishing posts, listing projects, and building custom clients.
Blogizi exposes a small REST API used by the CLI, Obsidian plugin, and any custom client you build. For agent tool calling, see the MCP docs. Base URL: https://blogizi.com.
Start here
- Authentication — account API keys and project selection
- Create or upsert post —
POST /api/posts - List projects —
GET /api/account/projects
Endpoint groups
- Posts — create, upsert, and list posts with an account API key
- Projects — list blogs for the authenticated account
- Search — Google Search Console performance for a bound project (
GET /api/search-analytics) - Public blog — unauthenticated routes used by the live blog UI (listing, search, analytics, domain resolve)
Not covered here
Dashboard-only routes (domains, themes, billing, upload, and post PATCH / DELETE by id) require a signed-in session cookie and are not part of the public API key surface.
CORS
Account API key routes used by the Obsidian plugin respond to OPTIONS preflight and allow browser clients. Prefer the CLI or Obsidian's requestUrl for production tooling.
Prefer the CLI when possible
For repo-based workflows, agents should write markdown and shell out to blogizi draft / blogizi publish instead of hand-rolling HTTP — unless you are integrating the API into your own app.