Add a blog to your product, choose the right interface, and move from setup to published delivery.

Cli Blog adds publishing to a website or application without requiring your team to build a CMS. Editors work in the dashboard. Developers, CI jobs, and agents use the REST API, Node SDK, CLI, or agent skill. Published content returns as structured JSON for your frontend to render.

Start with an outcome

Publish the first post

Create an author, category, and tag; draft a post; publish it; and read it from a frontend.

Create an agent workflow

Inspect existing content, create a complete draft, collect approval, publish, and verify delivery.

Set up the organization

Configure publication settings, create keys, invite members, review activity, and manage billing.

Add a blog to Next.js

Follow a full server-rendered delivery and publishing tutorial, then choose another framework from the guide navigation.

Choose an interface

Interface	Description	Start here
Dashboard	Set up the organization, write and review posts, manage members and keys, and see billing	Dashboard and billing
REST API	Read or manage content from any technology that can send HTTP requests	Posts
Node SDK	Use typed resource methods from Node.js 20+ servers, scripts, CI jobs, and agents	Node SDK
CLI	Run publishing commands and JSON workflows from a trusted terminal	CLI
Agent skill	Give supported agents Cli Blog context, tool choices, key rules, and approval gates	Agent skill

You can combine them. An agent can create a draft with the Node SDK, an editor can review it in the dashboard, a release job can publish it with the CLI, and a website can read it through the REST API.

Compare boundaries and common tasks on the Tools page.

Browse resources and API details

Each resource guide explains what the resource is for, compares REST, SDK, and CLI actions, lists important fields, and embeds the generated endpoint schemas.

Posts

Markdown, workflow, relationships, SEO, filters, fields, and includes.

Revisions and redirects

Earlier post versions and redirects from changed slugs.

Authors

Public byline profiles for one or more post authors.

Media

Uploaded images, files, metadata, and post relationships.

Locales

The curated BCP 47 tags accepted by localized content.

Sitemap

XML discovery for published, indexable posts.

Feed

RSS XML for published posts in one locale.

The generated endpoint schemas remain available when you need the exact OpenAPI request and response definitions.

Learn the shared concepts

API keys

Choose public or private keys, limit permissions, rotate credentials, and handle exposure.

Pagination

Follow cursors for efficient traversal or opt into exact numbered pages.

FAQs

Find answers about Markdown, browser delivery, locales, webhooks, errors, teams, and billing.

Use predictable API conventions

Send organization API keys in the x-api-key header.
Use public keys for published-content delivery.
Use private keys only in trusted servers, CI jobs, local shells, and agent environments.
Send JSON request bodies except direct media upload, which uses multipart/form-data.
Put filtering, sorting, pagination, field groups, and includes in query parameters.
Use POST for create and update operations.
Use DELETE for delete operations.
Keep locale explicit when the same slug can exist in more than one language.

Production examples use https://api.cli-blog.com.

Introduction