API · Content

Content API

Website content nodes, versions, values, and related routes used by the SDK and prerender — authenticated with X-Api-Key.

API keywebsite

Interactive: Swagger · Content · JSON: /docs/specs/content.json

Auth

Send X-Api-Key with a PUBLIC (pk_) or DEVELOPMENT (dk_) key. Legacy SECRET (sk_) keys still work for server prerender/CI. For new automation that writes content, prefer Managementmt_ tokens.

When to use

Browser SDK hydration and store-component runtime loading
Build-time prerender / SSR content injection
Read live or draft values during a custom integration

Representative endpoints

GET/content/valuesAPI key

Fetch content values for the website key context (SDK / prerender).

GET/content/store-nodes/runtimeAPI key

Runtime definitions for installed Store components (SDK loadStoreComponents).

GET/content/nodesAPI key

Node definitions and structure for the website.

Editor routes are separate

Overlay sessions use editor endpoints (site-user login), not Management tokens. See the Editors handbook for the human flow and Keys & config for key types.

bash

curl -sS "https://api.macrocontent.dev/content/values" \
  -H "X-Api-Key: pk_..."