Your first backend in 10 minutes

This walkthrough takes you from an empty workspace to a working, documented API. No SDKs, no boilerplate, just the platform.

1 · Create a project

Sign in and hit New project. A project is an isolated workspace: its own endpoints, API keys, files, team and documentation. Starting from a template (blog, e-commerce, SaaS starter) pre-builds typical endpoints. For this tutorial, start blank and name it demo-shop.

2 · Model your first resource

Go to Endpoints → New, choose type Resource (a headless-CMS table), slug products, and add fields:

title     text      (required, searchable, show in list)
price     number    (required, min: 0)
summary   textarea
image     image
status    select    (draft / published)

Every field type carries validation: the gateway enforces it on writes, the editor enforces it in forms.

3 · Add content

Open the endpoint's Data tab and add a few records, or use Import to paste CSV/JSON. Records support drafts, revisions and (if you enable it later) multiple languages.

4 · Create an API key

API Keys → New key. Copy it now; it's shown once. Keys are project-scoped and hashed at rest.

5 · Call your API

curl "https://YOUR_HOST/api/gateway/demo-shop/products?filter[status]=published&sort=-created_at" \
  -H "Authorization: Bearer YOUR_KEY"

You get a consistent envelope with data, meta pagination and a request_id for tracing. Filtering, search (?search=), sorting and relationship embeds all work out of the box.

6 · Share the docs

Each project auto-generates public API documentation at /docs/{slug}: endpoints, example requests, auth instructions. Send it to your frontend dev and you're done.

Next: let your AI do all of the above; see Let Claude build your backend.