Update a contact memory entry

Create or replace the memory entry with this name; the entry is upserted, so a PUT to a name that does not exist yet creates it. This is a full replace, not a patch: omitting description clears the stored description. Returns { ok: true, entries: <count after the write> }; invalid input returns 400 and an unknown session 404. Staff writes work even when the project’s contact-memory feature is disabled.

PUT /sessions/{sessionId}/memory/{entryName}

Update a contact memory entry

cURL

curl --request PUT \
  --url https://api.gleap.io/v3/sessions/{sessionId}/memory/{entryName} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'project: <project>' \
  --data '
{
  "content": "<string>",
  "description": "<string>"
}
'

200

{
  "ok": true,
  "consolidationEnqueued": true,
  "entries": 123
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

project · string · required

Path Parameters

sessionId · string · required

entryName · string · required

Body

application/json

content · string · required

Required. Truncated to 4000 characters.

description · string

Optional. Omitting it clears the stored description; this is a full replace, not a patch. Truncated to 240 characters.

Response

200 - application/json

Ok

ok · boolean · required

reason · enum<string>

Only set on internal (non-admin) calls; never present in an admin API 200 response.

Available options: disabled, no_userId, invalid_input, session_not_found

consolidationEnqueued · boolean

entries · number<double>