Everything you need to build with C for CMS.

1. Create a project

Sign in to the Studio, create an organization, and add a project. Each project gets an isolated schema and its own set of API keys.

2. Define a content type

In the Studio, create a content type called blog-posts with a title (Text), body (Rich Text), and status (Select). Save to publish the schema — your APIs update instantly.

3. Query the API

Generate an API key with content:read scope, then fetch your entries:

curl 'https://api.cforcms.com/api/v1/my-project/blog-posts?limit=10' \
  -H 'X-API-Key: sk_live_a1b2c3d4e5f6'

API keys

API keys are scoped to a single project and carry a set of permission scopes. Pass the key in the X-API-Key header on every request.

curl 'https://api.cforcms.com/api/v1/my-project/blog-posts' \
  -H 'X-API-Key: sk_live_a1b2c3d4e5f6' \
  -H 'Content-Type: application/json'

Scopes

Grant each key only what it needs: content:read, content:write, media:read, media:write, schema:read, schema:write, webhook:read, webhook:write, team:read, team:write.

Field types

• Text, Textarea, Rich Text, Number, Boolean, Date, DateTime
• Email, URL, JSON, Select, Multi-select
• Media, Media List, Relation, Repeater, Component

Relations & components

Use Relation fields to link entries across content types, Repeater fields for ordered lists of nested data, and Component fields for reusable groups of fields shared between types.

Draft & publish

Entries move through a draft → published lifecycle. The API returns published entries by default; request drafts explicitly with a content:write key.

Querying

GET /api/v1/my-project/blog-posts
  ?filter[status]=published
  &sort=-publishedAt
  &limit=10
  &populate=author

Responses are paginated with a meta block containing page, limit, total, and totalPages.

Uploads

Upload files via the Studio or the media API. Images get thumbnails generated automatically, and everything is searchable by type and folder.

Delivery

Attach media to entries with Media and Media List fields. Files are served through presigned URLs so you keep control over access.

Base URL

https://api.cforcms.com/api/v1/{project}/{contentType}

Response shape

{
  "data": [ /* entries */ ],
  "meta": { "page": 1, "limit": 10, "total": 42, "totalPages": 5 }
}

Add format=csv to any list request to export results as CSV instead of JSON.

Example query

query GetPosts($locale: String) {
  blogPosts(
    filter: { status: { eq: "published" } }
    sort: "-publishedAt"
    limit: 10
    locale: $locale
  ) {
    id
    title
    slug
    publishedAt
    author { name avatar }
  }
}

Payload

{
  "event": "entry.published",
  "timestamp": "2025-03-15T10:00:00Z",
  "project": "my-project",
  "contentType": "blog-posts",
  "entry": { "id": "post_8x9kL2", "status": "published" }
}

Verifying signatures

import crypto from 'crypto';

function verifyWebhook(payload: string, signature: string, secret: string) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex');
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected),
  );
}

Roles

• Organization — owner, admin, member.
• Project — admin, editor, viewer.

Invite team members to an organization and assign per-project roles so each person sees exactly what they should.

Capabilities

• Generate a content type from a natural-language description.
• Per-field actions: generate, improve, translate, summarize.
• SEO suggestions for titles, descriptions, and slugs.

The stack

• NestJS API server
• PostgreSQL with Prisma ORM
• Redis for caching and queues
• Cloudflare R2 (or any S3-compatible store) for media

Bring up the full stack with Docker Compose, or deploy the included manifests to your Kubernetes cluster for full control over your data.