Fetching content via API

If you’re pulling your content into your own website or app, you fetch it through the REST delivery API. Base URL: https://app.nevocms.com.

Authentication

Every request carries your workspace’s API key in the Authorization header:

Authorization: Bearer <API key of your workspace>

Endpoints

• GET /api/rest/<collection> – list the documents in a collection
• GET /api/rest/<collection>/<id> – a single document

List parameters

Parameter	Meaning
locale	only documents in this language
status	default: published
slug	filter by slug
search	full-text search over the title
sort / sortDir	sort field and direction (asc or desc)
page	page of results
limit	items per page, 1–500, default 25

Response shape

The list responds with { docs, total, page, totalPages }. Each document has id, slug, title, status, locale, data, publishedAt, updatedAt and translations. Rich-text fields arrive as Markdown, image fields as an object with url, path, alt, width, height and variants.

curl example

curl "https://app.nevocms.com/api/rest/posts?locale=en&status=published&limit=10" \
  -H "Authorization: Bearer <API key>"

fetch example

const res = await fetch(
  "https://app.nevocms.com/api/rest/posts?locale=en&status=published&limit=10",
  { headers: { Authorization: `Bearer ${API_KEY}` } },
);
const { docs, total } = await res.json();

Related topics

How to set up the fields that end up in data is covered in Collections and fields; how translations are structured, in Multiple languages.