Skip to main content
PATCH
Update customer memory

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access.

Path Parameters

id
string<uuid>
required

Audience contact ID.

Body

application/json
expected_revision
integer
required

Current workspace-memory revision returned by GET. Use 0 only when no workspace memory exists.

Required range: x >= 0
Available options:
unknown,
granted,
denied
summary
string | null
Maximum string length: 1500
preferences
object

Response

The updated customer-memory record.

data
object