Headless CMS

A Headless CMS With an API and CLI

What it is, how the API, SDK and CLI fit together, and how to publish your first post without opening a browser.

In short

Headless CMS with an API and CLI

A headless CMS with an API and CLI stores content as structured data instead of a fixed template, and lets you create, edit and publish it from code. The API moves data over HTTP; the CLI wraps common calls into short commands you or a script can run, including one an AI agent runs on a schedule.

How it works

A Worked Example: Creating and Publishing a Post From the CLI

  1. Authenticate

    Log the CLI into your Floggy account once. From then on, commands run against your workspace without a browser login step each time.

  2. Create a draft

    Run a command to start a new post with a title. The CLI sends this as an API call and returns the new post's ID, which you use in the next steps.

  3. Set the content and fields

    Fill in the body and any fields the collection defines, tags, a summary, a custom field for a programmatic SEO template, using flags or a content file passed to the CLI.

  4. Publish

    Run the publish command against the post ID. The post goes live on your blog immediately, the same as clicking publish in the editor, without opening the editor.

  5. Verify or automate further

    Read the post back through the API to confirm it published correctly, or chain the whole sequence into a script an agent runs unattended on a schedule.

What you get

What Custom Collections Let You Structure

  • Define content types beyond blog posts: product listings, comparison pages, city or category pages
  • Give every entry consistent fields, so a script can fill them in the same way across many entries
  • Query and filter collection entries through the API by field, not just by fetching the whole blog
  • Reuse one collection schema across many pages built from a template, which programmatic SEO runs on
  • Keep custom collections separate from your main blog, so structured and regular content don't collide
How it works

Getting Started with Floggy's CLI

  1. Install the CLI

    Add Floggy's CLI to your machine the same way you'd install any other command-line tool. It runs locally and talks to your Floggy workspace over the API.

  2. Authenticate once

    Log in from the CLI the first time you use it. It stores a token so later commands run against your workspace without asking you to sign in again.

  3. Connect it to your site

    Point the CLI at the Floggy site or workspace you want to manage. From here it knows which blog and which custom collections your commands apply to.

  4. Publish or sync your first piece of content

    Create a draft, fill in its fields, and publish it, or pull existing content back down to confirm it synced. One round trip is enough to know the CLI is wired up correctly before you script anything bigger.

Built for Developers and the Agents They Run

cli

$ floggy publish

post deployed 200

$ floggy posts list

GET /api/posts 200

$

Built for developers

Headless CMS, API, and a CLI to publish from anywhere with your favorite agent.

Scheduled

Publish with intent

Long-form posts, scheduled, co-authored.

Features

How This Fits Agentic and Programmatic SEO Workflows

  • Agents publish through the same API you'

    There's no separate 'agent mode.' An AI agent authoring or auto-publishing posts calls the same API and CLI a person would, which means anything you can script, an agent can run.

  • Custom collections give programmatic SEO

    Programmatic SEO depends on generating many pages from one structure. Custom collections are that structure: define the fields once, generate entries at scale through the API.

  • Scheduling turns a one-off script into a

    Because publishing is a CLI command, it can run on a schedule instead of a one-time push, so an agent can keep adding or updating content over time without manual triggering.

  • You keep the editor as a check

    Everything created through the API or CLI still shows up in the regular Floggy editor, so a human can review or edit anything an agent published.

Ready when you are

Set Up Your Blog and Try the CLI

Sign up free, get a workspace with a blog and custom collections, and connect the CLI or SDK when you're ready to script or automate publishing.

Get started

  • Your own domain

    Everything lives at an address you control.

  • Nothing to wire up

    Publishing, audience and analytics ship together.

  • Reach inboxes

    A newsletter and a subscriber list, built in.