Overview

Use the Elements CMS JSON REST API for headless frontends, apps, and scripts.

The Elements CMS Online Editor includes a token-authenticated JSON REST API for headless use. Your apps, mobile clients, static builds, and migration scripts can read and write CMS content over HTTPS with a simple Authorization: Bearer api_... header.

If you want Claude, Cursor, or another AI assistant to manage the CMS through conversation, use the MCP Server instead.

Studio / JSON API access is required. Every /api/* route, including public reads, requires an active license for the site's domain with JSON API access enabled. Without one, every request returns 402 Payment Required.

Start here

• Installation - prerequisites and how to verify the API is reachable.
• Authentication and API Keys - creating keys in the Online Editor, header format, and how API keys differ from MCP tokens.
• Quickstart - a short walkthrough: list, create, update, and delete CMS content.

Choose your path

Building this	Start here
Headless frontend, static site, or SPA	Headless Frontend
Mobile or desktop client	Authentication, then Items
Bulk migration script	Content Migration
Upload integration	Uploads
Webhook receiver	Webhooks

Reference

The route reference is split by surface area:

• Reference Overview
• Collections
• Items
• Resources
• Versions
• Settings
• Search and Feeds

Errors and versioning

• Errors - status codes, response shapes, and troubleshooting.
• Changelog - API versioning policy and notable changes.