supermemory/apps/docs/v5/api-reference/overview.mdx
MaheshtheDev 5dd459e9f7 docs: full drift audit (2026-10-27)
Align API, guide, SDK, plugin, tools and billing pages with the live code in mono, sdk-ts, python-sdk, the plugin repos, smfs and memorybench.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-10-27 23:50:30 +00:00

50 lines
1.8 KiB
Text

---
title: "API reference"
sidebarTitle: "Overview"
description: "Documents, search, profiles, lists, memories, connectors, namespaces, and organization settings in the latest Supermemory API"
icon: "/icons/hugeicons/plug-socket.svg"
---
import MigrateCli from "/snippets/migrate-cli.mdx";
v5 makes namespace scope explicit in the URL and consolidates overlapping legacy operations.
```text
https://api.supermemory.ai
/ns/{namespace}/document
/ns/{namespace}/search
/ns/{namespace}/profile
/ns/{namespace}/list/{type}
/ns/{namespace}/memories
/ns/{namespace}/connectors
/connectors
/namespaces
/organization
```
<MigrateCli legacy="v3 or v4" guideHref="/migration/api-v5" guideLabel="v5 migration guide" />
Use the [v5 reference](https://api.supermemory.ai/v5/reference) for the stable v5 API. [`/reference`](https://api.supermemory.ai/reference) always points to the latest public version.
## Install the TypeScript SDK
```bash
npm i supermemory
```
```ts
import { Supermemory } from "supermemory"
const supermemory = new Supermemory({ apiKey: process.env.SUPERMEMORY_API_KEY })
```
URL values are positional arguments (`namespace` first, then `id` where there is one), and everything else goes in one object: `supermemory.add("user_123", { content })`. Each reference page below shows the SDK call next to the equivalent `curl`. The Python SDK (`pip install supermemory`, 5.0.0 and later) follows the same shape with keyword arguments: `client.add("user_123", content="...")`.
<CardGroup cols={2}>
<Card title="Migrate to v5" icon="arrow-up-right" href="/migration/api-v5">
Translate every v3/v4 request and response deterministically.
</Card>
<Card title="Authentication" icon="key" href="/authentication">
Authenticate with the same bearer API keys used by legacy endpoints.
</Card>
</CardGroup>