1. Create a content type
Define fields with stable IDs — the schema an editor and an API consumer both rely on.
DevelopersGETTING STARTED
From content model to live API, in minutes.
The content layer is a REST API over JSON. There's no SDK to install and no framework-specific client — define a content type, generate a page, and fetch it with a plain HTTP call from whatever's already rendering your frontend.
01 / THE SHAPE OF IT
Four steps to a first request
Create a workspace, define a content type, add a record, and bind a template — then the same published page is one GET request away.
2. Add a record & bind a template
Create a record, bind a template to it, and preview the generated page before it publishes.
3. Fetch the published page
Call the site's public content API for that page — plain JSON, same shape in every environment.
02 / NO SDK, NO LOCK-IN
Works with the stack you already have
Static generation, server rendering, or a client-side fetch — nothing about the API assumes a particular framework or hosting target.
Same API everywhere
Local, staging, and production all talk to the same versioned /v1 API — no environment-specific client code to maintain.
Any rendering strategy
Fetch at build time, at request time, or from the browser — the API doesn't care which.
Standard HTTP auth
Authenticate with a workspace session or a scoped API key — no custom handshake to implement.
MAKE YOUR FIRST REQUEST
Fetch a real published page.
Open a workspace, generate a page, and call the public API against it.