---
title: "Update Copilot Personal Wiki Sources"
method: PUT
path: "/copilot/personal-wiki/sources"
tags: ["Copilot"]
---

# Update Copilot Personal Wiki Sources

`PUT /copilot/personal-wiki/sources`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/copilot/personal-wiki/sources`
- Auth: HTTP bearer

Change what the assistant may read.

PARTIAL: an omitted field is left alone, an explicit one changes it. So
omitting `email_enabled` and sending `false` are different instructions.

SWITCHING A SOURCE OFF DOES NOT UNLEARN. It stops new facts arriving from
there; what was already derived stays until it is forgotten one fact at a
time through `POST /copilot/personal-wiki/forget`.

## Headers

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

## Request body

- PersonalWikiSourcesUpdateRequest: Mirror of `PersonalWikiSourcesUpdateRequest`. PARTIAL: the handler applies `exclude_unset`, so an omitted field is left alone and an explicit value changes it. Sending `email_enabled: false` is not the same instruction as omitting it.
  - `primary_mailbox_id` integer, nullable: The mailbox the wiki draws its email signal from.
  - `additional_mailbox_ids` integer[], nullable: Further mailboxes to read.
  - `email_enabled` boolean, nullable: Whether the Copilot reads your email to build the wiki. Turning this off stops new facts arriving from email; it does not remove what it already learned - use `POST /copilot/personal-wiki/forget` for that.
  - `calendar_enabled` boolean, nullable: Read your calendar.
  - `docs_enabled` boolean, nullable: Read the named documents.
  - `document_ids` string[], nullable: Which documents, when `docs_enabled`.
  - `work_enabled` boolean, nullable: Read your Work activity.

## Response `200`

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/89fc11143b70?raw)