---
title: "What the Memory API does"
description: "Send timestamped text, wait for it to complete, then recall ranked memory with the data points behind it."
canonical: https://past.dev/docs/memory-api/overview
last-updated: 2026-10-09
---
# What the Memory API does

> Send timestamped text, wait for it to complete, then recall ranked memory with the data points behind it.

Product: past.dev Memory API. Source: https://past.dev/docs/memory-api/overview

You send past.dev data points: pieces of text with the time each one happened, such as a call transcript, an email or a CRM note. past.dev derives memory from them. A recall names a reader and a question, and returns evidence: the documents that answer, each a memory with the excerpts of the data points behind it, or a data point itself. An audience decides which readers may see a data point.

The API accepts text from conversations, email, meetings, support records, CRM notes and documents. Each data point keeps your source id and its occurrence time. Recall returns ranked documents with dates, artifact context and the exact excerpts of the data points behind each document.

Five nouns organize every call. A project is the isolation boundary, and a project key selects one. A data point is one thing that happened, sent with its own time. An audience is the scope that decides which identities can read a data point. An identity is the reader a recall answers as. A trait is an attribute of an identity that audience rules match on. [Concepts](/docs/memory-api/concepts) defines each one.

Read the [Quickstart](/docs/memory-api/quickstart) first, then [the Setup page](/docs/memory-api/setup) for the complete procedure in order. Read [Sending data](/docs/memory-api/sending-data) before a historical load and [Access control](/docs/memory-api/access-control) before the first customer goes live.

All routes use JSON under `/api/v1`. The [API reference](/docs/memory-api/api-reference) documents every operation, and the same contract is machine-readable at [/openapi.json](/openapi.json).

- `POST /api/v1/ingest` accepts one data point, and `POST /api/v1/ingest/batch` accepts an ordered batch of up to 1,000. `GET /api/v1/ingest/{ingestionId}` reports completion and `DELETE` on the same route forgets the send.
- `POST /api/v1/recall` returns ranked documents for one identity.
- `DELETE /api/v1/data-points/{sourceId}` and `POST /api/v1/data-points/delete` delete data points by your own source id.
- `POST /api/v1/webhooks/{webhookId}/{token}` receives an event from another system. [Webhooks](/docs/memory-api/webhooks) describes the mapping and the filters.
- `/api/v1/audiences` creates, reads, replaces, deletes and recomputes audiences by slug.
- `/api/v1/identities` creates, updates, bulk-replaces, lists, reads and deletes identity records and their traits.
- `/api/v1/projects` lists and creates projects and mints or revokes project keys. These routes take the management key.

**Get API key.** Sign up and start with 150,000 credits, 400,000 with a work email. No card required, and nobody approves the account. Create project keys in the console. Get API key: https://sso.past.dev/sign-up