Skip to main content
PATCH
Add a session to memory
Configure a memory backend first and provide a valid sessionId under the same application and user. An unconfigured memory service returns 400; a missing session returns 404
This operation sends session events to the configured memory service for storage or processing. Future retrieval can use that content. Confirm that the session data is appropriate for the selected backend before submitting it
A successful response is JSON null, indicating that the ingestion call completed. It does not return extracted memories or guarantee a match in subsequent retrieval

Authorizations

Authorization
string
header
required

Optional locally without a gateway; cloud deployments use the Runtime API key or user-pool JWT required by that deployment, never the model API key

Path Parameters

app_name
string
required

Application name; harness_agent for the CLI deployment

user_id
string
required

User ID

Body

application/json
sessionId
string
required

Session ID

Response

Successful response

Last modified on September 19, 2026