Public API/Overview/API Overview
Public API

API Overview

HTTP API for drafting, scheduling, and publishing posts, listing projects, and building custom clients.

Blogizi exposes a small REST API used by the CLI, Obsidian plugin, n8n community node, and any custom client you build. For agent tool calling, see the MCP docs. Base URL: https://blogizi.com.

Start here

Endpoint groups

  • Posts — create, upsert, list, and schedule posts (via scheduledAt), and upload cover/content images 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)

Scheduling

Post scheduling is part of the public API. Pass scheduledAt on POST /api/posts (and the project-scoped create route). There is no separate schedule endpoint for API keys — scheduling is a field on create/upsert.

  • A future scheduledAt keeps status: "draft"; Blogizi publishes at that time (do not poll or re-POST published early)
  • ISO with Z or an offset is absolute UTC; naive YYYY-MM-DDTHH:mm uses the project timezone (Settings → General)
  • scheduledAt: null clears a schedule; omit on upsert to leave the existing schedule unchanged
  • status: "published" publishes immediately and cancels any pending schedule
  • Responses return UTC ISO scheduledAt (or null); internal queue ids are never exposed
  • List posts includes scheduledAt on each item — scheduled posts still show as draft

Agents / MCP also have schedule_post for changing only the go-live time. CLI: frontmatter scheduledAt or --scheduled-at / --unschedule — see CLI publishing.

Not covered here

Dashboard-only routes (domains, themes, billing, logo/favicon 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.