The CMS API turns any list of structured data on your site into a managed collection. Define a schema once, then create, update, and list items via a single set of endpoints. Every collection is a namespaced bucket scoped to your organization. Items inside a collection are JSON objects validated against the collection’s schema before they are stored.Documentation Index
Fetch the complete documentation index at: https://kardow.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why use it
- No new tables. Add a sponsors page, a courses catalogue, or a directory in minutes — no migration required.
- Validation built-in. Each field has a type (
text,image,url,select,date, …). Bad data is rejected at the API boundary. - Public read out of the box. Public collections are cached at the edge for 60 seconds and revalidate automatically when you write.
- Monetizable. Pair a collection with a
payment_planwhosepurposeiscms_itemand visitors can pay to add an entry (sponsorships, classifieds, featured listings, …).
Authentication
All CMS endpoints accept an API key via thex-api-key header. Required
permission scopes:
| Scope | Endpoints |
|---|---|
cms:read | GET endpoints |
cms:write | POST, PATCH, DELETE endpoints |
* permission) work for every CMS endpoint.
Get your API key from Dashboard → Settings → API Keys. When creating a
key for CMS automation, scope it to
cms:read and cms:write only.Field types
| Type | Notes |
|---|---|
text | Single-line, default max 5,000 chars. |
longtext | Multi-line, default max 100,000 chars. |
number | JSON number. Use min/max for bounds. |
boolean | true / false. Strings "true"/"false" accepted. |
image | URL or storage path (/bucket/object.png). |
url | Must start with http:// or https://. |
select | Requires options: string[]. |
date | ISO 8601 timestamp. |