Entries

Entries are your content. The REST API lists and fetches them by content type and slug, lists them across every type, and creates new drafts. Updating, publishing and deleting entries is done over GraphQL.

Every endpoint here accepts ?environment=staging and ?locale=.

List entries of a type

GET /v1/content/:type

The endpoint most sites use. :type is the content type's slug.

curl "https://api.graphcms.io/v1/content/blog-posts?limit=10&offset=0" \
  -H "Authorization: Bearer $GRAPH_API_KEY"

By default it returns published entries in en-US, newest first. Pass status or language to change that; see Querying.

{
  "success": true,
  "data": [
    {
      "id": "k3x9m2p7q1a4",
      "title": "Hello, world",
      "slug": "hello-world",
      "status": "published",
      "stage": null,
      "language": "en-US",
      "locale": "en-US",
      "publishedAt": "2026-09-30T14:02:11.000Z",
      "createdAt": "2026-09-30T13:55:40.000Z",
      "updatedAt": "2026-09-30T14:02:11.000Z",
      "fields": {
        "excerpt": "Our first post.",
        "body": "<p>Welcome to the blog.</p>"
      }
    }
  ],
  "pagination": { "limit": 10, "offset": 0, "total": 1 }
}

Needs content.view. Returns 404 with Content type not found for an unknown slug.

Get one entry

GET /v1/content/:type/:slug

curl https://api.graphcms.io/v1/content/blog-posts/hello-world \
  -H "Authorization: Bearer $GRAPH_API_KEY"

{
  "success": true,
  "data": {
    "id": "k3x9m2p7q1a4",
    "title": "Hello, world",
    "slug": "hello-world",
    "status": "published",
    "stage": null,
    "language": "en-US",
    "locale": "en-US",
    "publishedAt": "2026-09-30T14:02:11.000Z",
    "createdAt": "2026-09-30T13:55:40.000Z",
    "updatedAt": "2026-09-30T14:02:11.000Z",
    "contentType": { "id": "p8d2k4m9x0s1", "name": "Blog posts", "slug": "blog-posts" },
    "fields": { "excerpt": "Our first post.", "body": "<p>Welcome to the blog.</p>", "coverImage": null }
  }
}

stage is the workflow stage the entry is at, as { "id", "name" }, or null when its content type has no workflow (or the entry is archived).

fields has every field of the content type, in its order, so every entry of a type has the same shape: a field with nothing saved is null (or [] for a repeater or a multiple reference). Section fields only lay out the editor and aren't included.

Needs content.view. Returns 404 with Content type not found or Content entry not found.

This endpoint returns the entry whatever its status, drafts included. If your site should only show published content, check data.status === 'published' before rendering, or use the list endpoint, which filters to published by default.

List entries across types

GET /v1/content

Every entry in the environment, newest first, each with the content type it belongs to. Useful for sitemaps, search indexes and sync jobs.

curl "https://api.graphcms.io/v1/content?type=blog-posts&limit=50" \
  -H "Authorization: Bearer $GRAPH_API_KEY"

{
  "data": [
    {
      "id": "k3x9m2p7q1a4",
      "title": "Hello, world",
      "slug": "hello-world",
      "status": "published",
      "stage": null,
      "contentType": { "id": "p8d2k4m9x0s1", "name": "Blog posts", "slug": "blog-posts" },
      "locale": "en-US",
      "fields": { "excerpt": "Our first post." },
      "createdAt": "2026-09-30T13:55:40.000Z",
      "updatedAt": "2026-09-30T14:02:11.000Z",
      "publishedAt": "2026-09-30T14:02:11.000Z"
    }
  ],
  "pagination": { "limit": 50, "offset": 0, "total": 1 }
}

Unlike the per-type list, this returns entries of every status; filter on status yourself. Needs content.view. This endpoint doesn't send CORS headers, so call it from a server.

Create an entry

POST /v1/content

Creates a draft entry. Needs content.edit.

curl https://api.graphcms.io/v1/content \
  -X POST \
  -H "Authorization: Bearer $GRAPH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contentTypeSlug": "blog-posts",
    "title": "Release notes for October",
    "slug": "release-notes-october",
    "fields": {
      "excerpt": "What shipped this month.",
      "body": "<p>Lots.</p>"
    }
  }'

{
  "data": {
    "id": "z0q8w1e2r3t4",
    "title": "Release notes for October",
    "slug": "release-notes-october",
    "status": "draft",
    "contentType": { "id": "p8d2k4m9x0s1", "name": "Blog posts", "slug": "blog-posts" },
    "fields": { "excerpt": "What shipped this month.", "body": "<p>Lots.</p>" },
    "createdAt": "2026-10-09T09:12:00.000Z",
    "updatedAt": "2026-10-09T09:12:00.000Z"
  },
  "message": "Content entry created successfully"
}

Errors are 400 for a body that isn't JSON or is missing contentTypeSlug or title, a non-string slug, a fields value that isn't an object, or a reference to an entry that doesn't exist or isn't allowed, and 404 for an unknown content type.

To create an entry that is published straight away, set its language, or update and delete entries, use createContentEntry, updateContentEntry and deleteContentEntry over GraphQL.

Import and export

In the dashboard, Import / export on the entries page exports the entries your current filters show (up to 5,000) as CSV or Excel (.xlsx). It also imports a CSV or .xlsx file into one content type. Other file types aren't accepted, and a file can have up to 2,000 rows.

An export has the columns ID, Title, Slug, Status, Content type, Created, Updated and Published, then one column per field, named after the field. An export can be imported back as it is.

Importing takes three steps in one dialog:

1. Upload. Drop a file on the dialog, or browse for one.
2. Map columns. Choose the content type to import into. Each column in the file is mapped to Title, Slug, Status or a field, by name. You can change each mapping or set a column to not be imported. Title must be mapped, and so must every required field.
3. Preview. Every row is checked before anything is saved. Each row shows whether it will be new, update an entry, be skipped, or has errors. Cells with a problem are highlighted, and the reason is shown next to the row. Go back to fix the mapping, or import only the rows that are ready.

Each row becomes a draft in the base language, unless its Status is draft, published or archived. An empty slug is made from the title. A row whose slug already exists is skipped, or updates that entry if you turn on Update entries whose slug already exists. A later row with the same slug as an earlier one is treated the same way.

A blank cell leaves the field empty, and clears it when updating an entry.