Read content anywhere
The BetterCMS API and SDKs deliver published content to any framework, with a separate write API for creating and publishing it. Every entry shape is typed from your own content model rather than declared by hand.
Your stack. Your rules. Everyone moves faster.
What the API gives you
-
Read API for delivery
Pages, entries, assets and the markdown twin of a path. A delivery key returns published content and nothing else.
-
Write API for management
Create a page, publish it, add entries and upload media. A personal token carries your own permissions with it.
-
Typed for your framework
Adapters for Next.js and Astro read the same content. Codegen types every entry from your own model.
-
A stale write is refused
Every write carries the version it was based on. Publish and apply also require an idempotency key.
-
Errors with stable codes
A failure returns a problem detail body, not a bare string. Role denied, plan gated and stale version each have a code.
-
Webhooks keep a receipt
Every send records the status code, duration and attempts. The response body is kept, so a failure can be read back.
-
Two. A read API delivers published content to any framework, and a separate write API creates and publishes it.
-
Yes. Entry types come from your own content model, so the shape your code expects is the shape the model defines.
-
Not from the read API. Drafts render behind a preview link, so published and unpublished content cannot be confused.
-
Both, plus SDKs. Pick whichever suits the framework you are already in.