Copilot

Upsert Copilot Memory Document

Write a memory document WHOLE. This replaces, it does not merge.

visibility defaults to shared, which means the whole organisation's Copilot may draw on it. That is the app's default and it is the wider of the two, so it is what you get by not thinking about it - worth thinking about it.

put/copilot/memory/documents

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/copilot/memory/documents
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

subject_typestring required

organization | user | campaign | company | contact.

subject_idstring required

Which one.

file_kindstring required

soul - who the subject is. memory - durable facts. daily - the rolling journal.

contentstring required

The WHOLE document. This is an upsert, not an append: it replaces what is there. Use POST /copilot/memory/documents/append to add without replacing.

titlestring nullable

Display title.

visibilitystring

shared - the whole org's Copilot may draw on it. Defaults to shared, matching the app, so a document written without thinking about this is visible org-wide.

Response

Successful Response

dataCopilotMemoryPayload required

An open envelope for one memory, wiki or sharing answer.

Open because the personal wiki is a DOCUMENT whose sections follow what has been learned about a person, and because each fact carries provenance - which mailbox or meeting it came from - that grows as new sources are connected. Pinning the shape would silently drop the provenance on the newest source, and on a "what do you know about me" surface a fact with no visible origin is worse than no fact.

Changes

No recorded changes to this operation across all 3 revisions of this API.