> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engramme.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Source Types

> Valid source_type values for memory data

Use `source_type` to describe where uploaded content came from. Source types also control source-scoped API key access.

## Valid Values

```text theme={null}
text, email, pdf, stream, browser, vscode, calendar, github, slack,
asana, claude_code, cursor, codex, google_meets, technical_docs,
weekly_updates, gdocs, tasks, contacts, youtube, photos, books, fit,
ms-outlook, ms-calendar, ms-teams, ms-onedrive, ms-sharepoint
```

## Common Choices

| Use case                                               | `source_type`  |
| ------------------------------------------------------ | -------------- |
| Plain text notes, exported docs, or quickstart uploads | `text`         |
| PDF files                                              | `pdf`          |
| Email content                                          | `email`        |
| Google Meet transcripts                                | `google_meets` |
| GitHub repositories, commits, or issues                | `github`       |
| Slack messages                                         | `slack`        |
| Cursor sessions                                        | `cursor`       |
| Claude Code sessions                                   | `claude_code`  |

## Notes

* If omitted, uploads default to `text`.
* A source-scoped API key must include the request's source type.
* Integration provider names and `source_type` values are not always the same. Use this list for REST API requests.