---
title: "How much of this store has been altered (alias of /api/v1/won/revisions)"
method: POST
path: "/api/v1/memory/revisions"
tags: ["memory"]
---

# How much of this store has been altered (alias of /api/v1/won/revisions)

`POST /api/v1/memory/revisions`

## Request

- Base URL: `https://api.wontopos.com`
- URL: `https://api.wontopos.com/api/v1/memory/revisions`
- Auth: API key in header `X-API-Key`

The original path for this call, kept for good: wontopos-mcp 1.0.14 and every client published before 2026-08-18 call it here. Identical behaviour, identical rate-limit budget — see /api/v1/won/revisions for the full description.

## Headers

- `X-WOS-Model` string

## Request body

- object
  - `user_id` string, required: The store to operate on. Stores are explicit: create one first or use the built-in "default". Use the id the store was created with: 1-64 ASCII letters, digits, ., _ or -, starting with a letter or digit. Ids that differ only by case name one store.
  - `include` 'revised' | 'unrevised': Omit for counts only. Set it to also receive ONE page of the memories behind that number. Only one of the two per call — there is no way to ask for both lists in a single response. An unrecognised value is rejected rather than silently ignored, because a typo that quietly drops the list looks exactly like an empty store.
  - `limit` integer: Memories per page, when `include` is set. 20 is both the default and the ceiling; a larger value is rejected, not clamped.
  - `before` string, date-time: Cursor: `next_before` from the previous page. RFC3339 — an epoch number is rejected, because silently ignoring it would hand back page 1 forever.
  - `skip_ids` string[]: Cursor: `next_skip_ids` from the previous page. Hand back what you were given — these are the ids already seen at the boundary timestamp, and dropping them makes the pager repeat itself.

## Response `200`

Success.

- object
  - `revised` integer: Memories a transform has touched.
  - `unrevised` integer: Memories nothing has touched since they were written.
  - `total` integer: Memories in the store. Always `revised + unrevised`.
  - `counts` string
  - `excludes` string
  - `include` string: Echoed back only when a page was requested.
  - `matched` integer: TOTAL memories behind this page (equal to `revised` or `unrevised`), not the size of the page. Only present with `include`.
  - `memories` object[]: One page, at most 20. Only present with `include`.
  - `has_more` boolean
  - `next_before` string, nullable
  - `next_skip_ids` string[]
  - `ordered_by` string: Which order the page is in — by when each memory was STORED, not when it was edited. Stated because assuming the latter would read the page wrong.

## Other responses

- `401`: Missing or invalid API key.
- `404`: Store (user_id) does not exist. Create it first: POST /api/v1/memory/collection.
- `429`: Rate limited (per-account, per-tier RPM). Retry after the indicated delay.

---

[API](https://skmtc.dev/wontopos/apis/wontopos-memory-api.md) · [All operations](https://skmtc.dev/wontopos/apis/wontopos-memory-api/llms.txt) · [OpenAPI document](https://skmtc.dev/wontopos/apis/wontopos-memory-api/revisions/48dda7326a33?raw)