Ingest conversation memory
Memory
Ingest conversation memory
Write turns under a scope. Active memory is saved first; enrichment continues in the background.
POST
Ingest conversation memory
This is the REST version of
Response —
tex.conversations.remember. Use it to write turns under a scope. Tex saves active memory first, then continues enrichment in the background.
Headers
Body
Your org id. Minimum length is 1 character. The server still uses the JWT’s
org_id claim for tenancy; this field is required for request validation.End-user partition. Defaults to the JWT’s user.
Conversation/channel/task id. Defaults to the JWT’s
session_id if set, else "default-session".At least one turn (
min_length=1). Each turn: {role, text, timestamp, observations?}. See How memory works.Optional write toggles:
{ write_active: bool = true, write_passive: bool = true }. Advanced callers can disable one storage tier.Free-form metadata. It is stored today and reserved for future filters.
Response — 202 Accepted
Stable id for this write.
Active-memory fragment ids. These are already recallable.
Background enrichment job id, when one is needed.
{tokens_in, tokens_out} billed for this call.Response
Example
Idempotency
Tex computes a stable hash per turn fromrole, text, and timestamp. Re-sending the same turn is a no-op. It does not create duplicate fragments or double bill the turn. It is safe to retry after a network failure.
