Approve a review item (admin) and apply it to the inventory.
const url = 'https://example.com/api/memories/reviews/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/approve';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"reason":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/memories/reviews/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/approve \ --header 'Content-Type: application/json' \ --data '{ "reason": "example" }'Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Review item ID
Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{ "reason": "example"}Responses
Section titled “Responses”Approved review result with optional applied memory
object
object
#1228 slice 2 (mig 369) — bi-temporal validity, Zep pattern: since when this
memory states something (backfilled to created_at).
… and until when. None = still valid; a supersede/merge/conflict apply
STAMPS this instead of deleting — the row stays readable and auditable while
the retrieval paths stop serving it.
object
#1392 — the producer’s CONFIDENCE in this proposal, 0..1, or NULL when the
producer has no honest signal (closeout reports, outcome-heuristic candidates,
agent/manual proposals that name none). Council candidates carry the judge’s
own judge_confidence. Distinct from proposed_importance: importance says how
much a memory matters, confidence says how sure the producer is. The review
detail renders the value, or an explicit “Unknown” when this is NULL.
#903 — the proposal’s own short TITLE (“Closeout: proposed_text,
which is the agent’s summary — so every row read as a sentence fragment.
NULL on pre-#903 rows; the frontend then falls back to the closeout evidence’s
task title and finally to the text snippet.
Examplegenerated
{ "memory": { "archived_at": "2026-04-15T12:00:00Z", "created_at": "2026-04-15T12:00:00Z", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "importance": 1, "last_used_at": "2026-04-15T12:00:00Z", "memory_kind": "example", "pinned": true, "project_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "salience": 1, "scope": "example", "source_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source_type": "example", "superseded_by": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "text": "example", "updated_at": "2026-04-15T12:00:00Z", "user_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "valid_from": "2026-04-15T12:00:00Z", "valid_until": "2026-04-15T12:00:00Z", "version": 1, "workspace_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }, "review": { "action": "example", "applied_memory_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "created_at": "2026-04-15T12:00:00Z", "created_by": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "evidence": "example", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "proposed_confidence": 1, "proposed_importance": 1, "proposed_memory_kind": "example", "proposed_pinned": true, "proposed_project_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "proposed_scope": "example", "proposed_text": "example", "proposed_title": "example", "reason": "example", "related_memory_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "reviewed_at": "2026-04-15T12:00:00Z", "reviewed_by": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "source_type": "example", "status": "example", "target_memory_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "updated_at": "2026-04-15T12:00:00Z", "workspace_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }}Structured client error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Authentication required
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Permission denied
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Structured server error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}