---
title: "Append Copilot Memory Document"
method: POST
path: "/copilot/memory/documents/append"
tags: ["Copilot"]
---

# Append Copilot Memory Document

`POST /copilot/memory/documents/append`

## Request

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

Add to a memory document without replacing it.

Defaults to the `daily` journal, which is where observations belong: the
durable documents are meant to be curated from it by
`POST /copilot/memory/promote`, not written to directly on every event.

Takes a JSON BODY. The app takes these as query parameters, which would put
the text of a personal note into the URL.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- MemoryDocumentAppendRequest: A BODY for what the app takes as query scalars. See the module docstring.
  - `subject_type` string, required: What the document is about: organization, user, campaign, company or contact.
  - `subject_id` string, required: Which one.
  - `content` string, required: The text to append.
  - `file_kind` string: Which document to append to. `daily` is the rolling journal and is the default; `memory` and `soul` are the durable ones and are normally written through `PUT /copilot/memory/documents` instead.

## Response `201`

Successful Response

- ApiResponseCopilotMemoryPayload
  - `data` CopilotMemoryPayload, 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.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)