Most apps should use @cms0/cms0 instead of calling the runtime API by hand.
Use the raw API when you are debugging, integrating a non-JavaScript client, or checking runtime health.
Runtime API shape can depend on the published schema. Use the in-app API docs for exact request and response bodies.
Base URL
Examples:
Runtime base URLs
https://environment-key.example.com/api
https://app.example.com/api/content/environment-key
https://admin.example.com/api/contentCommon categories
| Category | Purpose |
|---|---|
/health | Runtime health check |
/schema | Schema publish and schema state |
/content | Content reads and writes |
/_graph | Graph-style content access used by the SDK |
/backups | Self-hosted backup operations |
/triggers | Self-hosted manual trigger operations |
Hosted public environment endpoints intentionally expose a smaller public surface than the full self-hosted admin runtime.
API docs UI
The admin UI includes API documentation pages for the active runtime. Use those generated docs for exact request and response shapes because content routes are schema-driven.
Authentication
API keys are sent as bearer tokens:
Authorization header
Authorization: Bearer cms0_...Success check
The runtime is reachable when GET /health succeeds with the same base URL and API key your app will use.