Pin or unpin a memory; a pinned memory is never an archive or consolidation candidate.
const url = 'https://example.com/api/memories/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/pin';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"pinned":true}'};
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/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/pin \ --header 'Content-Type: application/json' \ --data '{ "pinned": true }'Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Memory record ID
Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{ "pinned": true}Responses
Section titled “Responses”Updated memory record after pin/unpin
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.
Examplegenerated
{ "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"}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"}