Add a memory to a team member | Ellaworks

Create a durable memory for a team member from the explorer. Goes through the same MemoryStore the agent uses, so the 500-char cap, exact-content dedupe, per-agent live cap, and embedding all apply. Embedding is best-effort (recency-only when the org has no OpenAI provider).

Authentication

X-API-Keystring

API key supplied via the X-API-Key header. Takes precedence over bearerApiKey when both are present. Listed only on operations that actually accept a key.

AuthorizationBearer

Same organization API key supplied as a Bearer token in the Authorization header (Authorization: Bearer <key>). Compatible with OpenAI-SDK-standard clients. Accepted wherever this scheme is listed on the operation — not every endpoint; if both X-API-Key and Authorization: Bearer are present, X-API-Key wins.

AuthorizationBearer

Supabase session JWT from a signed-in browser session, supplied as Authorization: Bearer <jwt>. This is what the web app sends. It shares the Authorization header with bearerApiKey; the server distinguishes them by the ela_ prefix on API keys.

Path parameters

teamIdstringRequired

agentIdstringRequired

Request

This endpoint expects an object.

orgSlugstringRequired

contentstringRequired1-500 characters

visibilityenumRequired

Allowed values:

Response

any