Docs

API reference

Changelog

GET /v1/changes

Incremental cursor. Empty on 2026-09.2.

Markdown Full spec OpenAPI

Incremental cursor for caches that want to follow the release stream.

MCP: get_changes { "since": "<cursor>" }

When to use

You already ingested a release and want creates / updates / deletes / merges since a cursor.

Books 2026-09.2 is the first books load — that stream is empty until the next books release. Food 2026-10.2 is the first live food changelog: 127,333 update rows (foods that gained pack shots). Pass dataset=food.

Request

curl -sS -H "Authorization: Bearer $FDS_API_KEY" \
  "https://api.fulldatasets.com/v1/changes?since=0&limit=100"
Query Required Notes
since yes Opaque cursor from the previous next_cursor, or a starting token you persist
limit no Default 100, max 1000
dataset no books (default), food, movies_tv, or icons
ids no Comma-separated edition, food, or title ids (max 50). Only those rows since since.

Response `200`

{
  "changes": [
    {
      "entity_id": "fds_ed_…",
      "entity_type": "edition",
      "op": "update",
      "content_hash_before": "…",
      "content_hash_after": "…",
      "merged_into": null,
      "release": "2026-09.3",
      "observed_at": "2026-09-01T00:00:00.000Z",
      "cursor": "…"
    }
  ],
  "next_cursor": null
}

| entity_type | books: work · edition · contributor. food: food · brand. movies_tv: title · person | | op | create · update · delete · merge |

On merge, merged_into is the surviving id. Follow redirects.

Short-TTL cache (30s / 60s CDN).

Errors

Status code When
400 bad_request Missing since

See also