Skip to main content
The EDN Memory API is a REST API that gives your AI app persistent memory. Your app saves conversation turns to EDN, then asks EDN for the relevant memory before each model call, as a SIP.
New to EDN? The Quickstart takes you from an API key to your first SIP in a few minutes.

Base URL and authentication

All endpoints sit under one base URL, and every request sends your API key as a bearer token:

Endpoints

Save memory

Save conversation turns and selected assistant outputs as memory.

Manage memory

List, read, edit and delete memories, and see their history.

Retrieve

Build a SIP for your model, or search memory.

Documents

Upload documents for EDN to answer from.

Projects

Group documents and memory into separate project scopes.

Sessions

Manage conversations and store their transcripts.

Conventions

  • Format: request and response bodies are JSON. Document upload is the exception: it sends the file as a form upload (multipart/form-data).
  • IDs: EDN generates the IDs of memories, projects and project documents.
  • Session IDs: you choose session_id yourself.
    • Reuse it for every request in the same conversation. EDN creates the session the first time you use a new ID.
    • It must be 1 to 128 characters long.
    • It can contain letters, digits and these symbols: period (.), underscore (_), colon (:) and hyphen (-).
  • Timestamps: ISO 8601 strings in UTC, such as 2026-11-10T04:43:25+00:00.
  • Empty values: optional response fields may be null when no value is available.

Pagination

List endpoints use limit and offset. If you request a limit above the endpoint’s maximum, EDN returns the maximum allowed number of results. Listing projects and project documents returns every item.

Errors and rate limits

Versioning

The API version is part of the path: /api/v1. The API is currently in private beta, and breaking changes are announced to beta testers before they ship.