NewAI writing assistant now live in all plans — drafts, translations, alt text and slug generation.Read more →
How it works

Schema. Content. API. Done.

Define your content model in minutes, publish content with AI assistance, and connect any front-end through REST or GraphQL. No infrastructure to manage.

Getting started

From zero to live API in under an hour.

1

MODEL YOUR CONTENT

Open the Content Type editor and define your schema — fields, types, validations, locales. No code needed. Your TypeScript types and GraphQL schema generate automatically from what you build.

2

PUBLISH WITH AI ASSISTANCE

Editors create entries in a clean two-column interface. The AI writing assistant is available in every text field — expand a brief into a draft, translate across locales, generate SEO metadata, and fill alt text automatically.

3

CONNECT ANY FRONT-END

Fetch published content via REST or GraphQL. The TypeScript SDK handles pagination, link resolution, and retries. Deploy to Vercel, Netlify, or your own infrastructure — ContentGrid's CDN-cacheable API keeps response times below 50ms at the edge.

Schema

Your content model, your rules

Content Types in ContentGrid work like typed database tables — except the editor UI, REST endpoints, and GraphQL schema all derive from them automatically. Add a field in the Content Type editor and it's available everywhere immediately: in the entry form, in the Delivery API response, in the generated TypeScript types, and in the GraphQL schema.

  • 20+ field types: text, rich text, reference, media, slug, JSON, coordinates and more
  • Per-field validations: required, unique, regex, range, MIME type, and content type constraints
  • Localized fields stored per locale — shared fields shared across all locales
  • Schema migrations tracked and versioned via CLI migration scripts
CONTENT TYPE
BlogPost
6 FIELDS
titleTEXTrequired
bodyRICH TEXTlocalized
slugSLUGunique · auto
heroImageMEDIAoptional
publishedAtDATETIMElocalized
localeLOCALEfallback chain
TypeScript typesGraphQL schemaREST filters
DEFINE ONCE · RUNS EVERYWHEREAUTO-UPDATED
Publishing

Draft, approve, publish — in one place

Every entry has a two-plane status model: draft and published fields are stored separately. Editors see their working version; the Delivery API returns only the published version. Publish immediately, schedule for a future time, or route through an optional approval workflow.

  • Status machine: Draft → Changed → Published → Archived → Scheduled
  • Scheduled publishing at any future UTC datetime
  • Optional approval workflow: Draft → In Review → Approved → Published
  • Unlimited version history with side-by-side diff and one-click restore
STATUS MACHINE
DRAFT
CHANGED
PUBLISHED
VERSION HISTORY
v5
Published
A. Patel
14 May · 09:15
v4
Title updated
A. Patel
14 May · 09:08
v3
Body copy edit
J. Martens
13 May · 17:42
UNLIMITED HISTORY · DIFF + RESTORE1 CLICK
DRAFT. APPROVE. PUBLISH.SCHEDULED OK

See it working on your content

Book a 20-minute walkthrough — we'll model a Content Type from your use case live.

    How ContentGrid works — ContentGrid