API · POST
POST /v1/memory
Write to typed memory with scope, tags and retention.
Overview
POST /v1/memory
Writes a memory record. Memory is typed (not just blob text), scoped (per role / channel) and retention-policied. PII / PHI is tagged at write-time and access-checked at read-time.
All xyner API calls require an OAuth2 bearer token with the appropriate scope. Every request is identity-bound and audit-captured.
Request
Example request
{
"scope": "customer:CUST-014892",
"type": "preference",
"key": "channel-preference",
"value": "email",
"ttl_seconds": 31536000,
"tags": ["preference", "channel"],
"sensitivity": "internal"
}
Response
Example response
A successful response has shape:
{
"id": "mem_01H8Y",
"scope": "customer:CUST-014892",
"version": 1,
"written_at": "2026-04-12T09:21:45Z",
"expires_at": "2027-04-12T09:21:45Z"
}
Notes
Things worth knowing
Useful behavioural details for this endpoint.
- All endpoints support OpenTelemetry trace-context propagation via standard W3C headers.
- Idempotency keys are honoured for 24 hours (or longer for endpoints that explicitly support extended idempotency).
- Errors follow RFC 7807 problem+json with a stable error code in
type. - Every successful action produces one or more audit records, queryable via /v1/audit/query.
- Rate limits apply per-tenant; current limits are returned in
X-RateLimit-*response headers.
See also
Related endpoints and concepts
This endpoint is part of the broader xyner platform API. For an end-to-end view, see the platform overview and the documentation hub.
Get started
Ready to put autonomous agents to work?
See xyner in your environment with a guided executive demo.