Docscms
CMS & Content API
Technical CMS operations for content types, content, versions, and publishing.
Resolve the target application first and carry applicationId. Resolve environmentId as well for environment-scoped secrets, integrations, and configuration.
Prefer application-scoped CMS endpoints and verify a mutation by re-reading the affected content resource.
Published collection reads
http
GET /api/cms/collections/{collection}/items?applicationId={appId}&status=published
X-App-ID: {appId}
X-Client-ID: {confidentialClientId}
X-Client-Secret: {confidentialClientSecret}Server-rendered websites should use a confidential service client, or the AppKit SDK configured with clientId, clientSecret, and appId. Never expose a client secret in browser code. Use status=published when the consumer must receive published content only.