LitPage CMS API Access Is Live

LitPage now supports authenticated CMS API access for external content workflows.

This release introduces a production-ready content API for teams that want CMS API integration without forcing every editorial step through the UI. External tools, CI pipelines, internal platforms, and AI agents can now create, update, and publish content in LitPage with a workspace API key.

If you have been looking for a practical CMS API for content publishing, this is the first public v2 surface to use.

What ships in the LitPage content API

The current v2 release focuses on two API surfaces:

• workspace key management
• site content operations

Together they provide the minimum workflow most teams actually need from a CMS API:

1. create a workspace API key
2. choose the target site
3. create or update content through the content API
4. publish when ready

The production base URL is:

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

The main content route is:

/sites/:siteId/contents

What the CMS API supports today

The LitPage content API currently supports:

• create content
• update content
• list content
• fetch content by ID
• fetch content by slug
• publish content
• unpublish content

If type is omitted, the API defaults to BLOG, which makes it easy to use as a blog publishing API while still supporting a broader CMS content model.

Why CMS API access matters

Most content systems claim to have an API, but a create-only API is not enough for a real publishing workflow.

Teams usually need to:

• generate a draft
• refine the draft
• review the draft
• publish or unpublish it

That is why this release matters. LitPage now supports the flow that external tools actually need, not just a narrow one-time create request.

This is useful for:

• CMS API integration with internal tools
• scheduled publishing jobs
• reviewable CI publishing pipelines
• AI-assisted content creation and revision
• external editorial systems that need direct API access

Workspace API keys and content API access

External requests use workspace API keys.

The recommended authorization header is:

Authorization: Bearer YOUR_WORKSPACE_API_KEY

This format also works:

Authorization: ApiKey YOUR_WORKSPACE_API_KEY

The access model is intentionally strict:

• the route identifies the target siteId
• the key identifies the caller's workspaceId
• the server verifies that the site belongs to the same workspace as the key

That gives teams a practical content API key model without opening cross-workspace access.

Example: create content with the LitPage CMS API

curl -X POST "https://build.lit.page/api/v2/sites/YOUR_SITE_ID/contents" \
  -H "Authorization: Bearer YOUR_WORKSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "BLOG",
    "title": "Hello from LitPage API",
    "slug": "hello-from-litpage-api",
    "excerpt": "Created through the LitPage v2 content API.",
    "content": "# Hello from LitPage API\n\nThis post was created through the LitPage content API.",
    "language": "EN",
    "author": {
      "name": "LitPage Team"
    }
  }'

Example: update content with the LitPage API

Update support is the difference between a demo API and a usable publishing API.

With PATCH, external tools can revise generated copy, apply automated edits, correct SEO text, or improve a draft before publishing.

curl -X PATCH "https://build.lit.page/api/v2/sites/YOUR_SITE_ID/contents/YOUR_CONTENT_ID" \
  -H "Authorization: Bearer YOUR_WORKSPACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Hello from LitPage API, Updated",
    "excerpt": "Updated through the LitPage v2 content API.",
    "content": "# Hello from LitPage API\n\nThis post was updated through the LitPage content API.",
    "updateReason": "Refined the introduction and tightened the copy"
  }'

Example: publish content

Once a draft is ready, publish it with:

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

If your editorial workflow requires rollback or additional review, you can move content back to draft with the unpublish endpoint.

A practical CMS API integration workflow

One immediate use case is AI-assisted content publishing.

An agent can now:

1. generate a draft from product or campaign context
2. create the draft in LitPage through the content API
3. revise the draft through the update endpoint
4. publish the final version after review or policy checks

That makes LitPage much easier to use in modern content operations where drafting, editing, and release steps are partially automated.

LitPage CMS API documentation and next steps

This release is the beginning of LitPage CMS API documentation for external publishing workflows.

The important part is not only that API access exists. It is that the first version already supports the workflow developers actually search for:

• CMS API access
• CMS API integration
• content API key authentication
• content updates
• content publishing

If you already use LitPage to manage site content, you can now create a workspace key, point your tool at the v2 endpoint, and publish directly from the systems where your team already works.