Skip to main content
Flush
dry_run defaults to true. The first call reports what would be deleted. Send "dry_run": false to actually delete.
Target a date range, specific callers by id, or leave both out for everything. Deletions are tombstoned and take effect at once. This is the path to satisfy a data-erasure request: run it for one person, check the counts, then run it for real and keep the receipt.

Authorizations

Authorization
string
header
required

Your API key as a Bearer token, e.g. Authorization: Bearer vk_….

Path Parameters

agent_id
string
required

The agent's id, as GET /v1/agents returns it.

Body

application/json
last_updated_on
string | null

Erase memory last touched on this date. A selector, not a stored field.

last_updated_from
string | null

Erase memory last touched on or after this date.

last_updated_to
string | null

Erase memory last touched on or before this date.

subjects
string[] | null

Erase only these people, by subject id. Omit to cover everyone the filters match.

dry_run
boolean
default:true

Send true first. It reports exactly what WOULD be erased and deletes nothing — the only way to check a filter before an irreversible delete.

Response

Successful Response

What a flush did, or would do.

dry_run
boolean
required

Whether this was a rehearsal. true means nothing was deleted.

subjects
integer
required

How many people were affected.

facts
integer
required

How many facts were erased.

transcript_turns
integer
required

How many stored turns were erased.