LitPage API Access Is Live

LitPage now supports direct API access for content workflows.

This release adds a production-ready path for external tools, scripts, CI jobs, and AI agents to create and publish content without going through the editor UI for every step. If you want to connect LitPage to your internal workflow, a CLI, or an automated content pipeline, the platform can now accept authenticated API requests against your site.

What is now available

Two v2 API surfaces are now in place:

• workspace key management
• site content publishing

The key management flow lets a workspace create API credentials for automation. Those keys can then be used against the content API to create blog posts and other supported content types for a site inside the same workspace.

Why this matters

This makes a few important workflows much simpler:

• publish from AI coding agents or internal tools
• push content from CI or scheduled jobs
• connect external editorial systems to LitPage
• standardize repeatable publishing operations with code

Instead of treating publishing as a purely manual action, LitPage can now participate in a broader delivery pipeline.

The basic flow

The integration path is intentionally narrow:

1. Create a workspace API key in LitPage.
2. Choose the target site ID.
3. Send an authenticated request to the v2 content endpoint.
4. Publish the created content when ready.

The base v2 endpoint is:

https://build.lit.page/api/v2/

The main content route is:

POST /sites/:siteId/contents

Authentication

LitPage uses workspace API keys for external access.

Requests can be authenticated with either of these headers:

Authorization: Bearer 

or:

Authorization: ApiKey 

Bearer is the recommended format for new integrations.

Example: create a blog post

curl -X POST "https://build.lit.page/api/v2/sites//contents" \
  -H "Authorization: Bearer " \
  -H "Content-Type: application/json" \
  -d '{
    "type": "BLOG",
    "title": "LitPage API Access Is Live",
    "slug": "litpage-api-access-is-live",
    "excerpt": "LitPage now supports authenticated API access for external publishing workflows.",
    "content": "# LitPage API Access Is Live\n\nLitPage now supports authenticated API access for external publishing workflows.",
    "language": "EN",
    "author": {
      "name": "LitPage Team"
    }
  }'

After creation, the content can be published with:

curl -X POST "https://build.lit.page/api/v2/sites//contents//publish" \
  -H "Authorization: Bearer "

Scope and access model

The access model is intentionally strict:

• the path identifies the target site
• the API key is bound to a workspace
• the server verifies that the site belongs to the same workspace as the key

That means external tools can automate content safely without turning the API into a cross-workspace access surface.

What you can do today

The current v2 API supports:

• creating content
• listing content
• fetching content by ID
• fetching content by slug
• publishing content
• unpublishing content

The API defaults to BLOG when type is omitted, but the model is designed to support broader content workflows over time.

A practical use case

One immediate use case is AI-assisted publishing.

An agent can now:

1. generate a draft from product context
2. send the draft to LitPage through the content API
3. publish it automatically or leave it in draft for review

That turns LitPage into a system that fits cleanly into modern automation workflows instead of sitting at the end of them.

Start using it

If you already manage content in LitPage, you can now expose selected publishing workflows to code.

Create a workspace key, point your tool at the v2 endpoint, and publish directly to your site.