--- title: "Server API Endpoints" description: "The self-hosted server provides a FastAPI application bootstrap layer that initializes application state, registers routers, enforces rate limits, handles CORS, and maps validation errors. This HTT..." last_updated: "2026-10-11T17:37:10.257685+00:00" canonical_url: "https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/server-dashboard/server-api-endpoints" ---
Relevant source files The following files were used as context for generating this wiki page: - [server/main.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/main.py) - [integrations/opencode-plugin/opencode-mem0.ts](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/opencode-plugin/opencode-mem0.ts) - [integrations/openclaw/cli/commands.ts](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/openclaw/cli/commands.ts) - [server/routers/entities.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py) - [integrations/hermes-plugin-mem0/__init__.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/hermes-plugin-mem0/__init__.py) - [server/dashboard/src/utils/api-endpoints.ts](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts) - [integrations/agent-plugin-core/python/memory_core.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/agent-plugin-core/python/memory_core.py) - [mem0/memory/main.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/mem0/memory/main.py) - [integrations/antigravity-plugin/core/memory_core.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/antigravity-plugin/core/memory_core.py) - [integrations/claude-code-plugin/core/memory_core.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/claude-code-plugin/core/memory_core.py) - [integrations/mem0-agent-plugin/core/memory_core.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/mem0-agent-plugin/core/memory_core.py) - [server/dashboard/src/types/api.ts](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts) - [integrations/antigravity-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/antigravity-plugin/core/mcp_server.py) - [server/routers/api_keys.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py) - [mem0/client/main.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/mem0/client/main.py) - [integrations/claude-code-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/claude-code-plugin/core/mcp_server.py) - [integrations/kimi-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/kimi-plugin/core/mcp_server.py) - [integrations/agent-plugin-core/python/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/agent-plugin-core/python/mcp_server.py) - [integrations/openclaw/index.ts](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/openclaw/index.ts) - [integrations/claude-code-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/claude-code-plugin/core/telemetry.py) - [integrations/mem0-agent-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/mem0-agent-plugin/core/telemetry.py) - [integrations/antigravity-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/antigravity-plugin/core/telemetry.py) - [integrations/codex-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/codex-plugin/core/mcp_server.py) - [integrations/agent-plugin-core/python/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/agent-plugin-core/python/telemetry.py) - [integrations/mem0-agent-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/mem0-agent-plugin/core/mcp_server.py) - [integrations/cursor-plugin/core/mcp_server.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/cursor-plugin/core/mcp_server.py) - [integrations/cursor-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/cursor-plugin/core/telemetry.py) - [integrations/codex-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/codex-plugin/core/telemetry.py) - [integrations/kimi-plugin/core/telemetry.py](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/kimi-plugin/core/telemetry.py) - [integrations/mem0-agent-plugin/mcp.json](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/integrations/mem0-agent-plugin/mcp.json)
## Overview The self-hosted server provides a FastAPI application bootstrap layer that initializes application state, registers routers, enforces rate limits, handles CORS, and maps validation errors. This HTTP interface powers remote memory synchronization, project scoping, and administrative management across client SDKs and dashboard integrations. Sources: [server/main.py:178-342](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/main.py#L178-L342), [FastAPI Application](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/server-dashboard/fastapi-application) ## REST API Architecture and Routing ### Endpoint Inventory and Path Conventions The FastAPI server exposes modular REST endpoints grouped into distinct API submodules, each mounted under dedicated path prefixes. These route definitions integrate with Pydantic schemas and database models to handle authentication, manage programmatic keys, inspect aggregated entities, and record audit requests. The route endpoints map across core functional domains including authentication (`/auth`), memory management (`/memories`), system configuration (`/configure`), API key administration (`/api-keys`), request log telemetry (`/requests`), and entity browsing (`/entities`). Client integrations and dashboard interfaces reference these exact paths via centralized utility configurations and typed API client definitions. | Submodule | Path Prefix | Key Methods | Description | | :--- | :--- | :--- | :--- | | Auth | `/auth` | GET, POST | Setup status, registration, login, token refresh, profile inspection, password change, and onboarding completion | | Memories | `/memories` | GET, POST, DELETE, PUT | Memory CRUD operations, history inspection, reset triggers, and generation instructions | | Configure | `/configure` | GET, POST | System configuration and provider settings | | API Keys | `/api-keys` | GET, POST, DELETE | Active key enumeration, creation of new API keys with secret generation, and key revocation | | Requests | `/requests` | GET | Request log telemetry and audit querying | | Entities | `/entities` | GET, DELETE | Aggregated entity listing across user, agent, and run scopes, and cascading memory deletions | Sources: [server/routers/entities.py:12-16](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L12-L16), [server/routers/api_keys.py:14](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L14), [server/dashboard/src/utils/api-endpoints.ts:1-34](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L1-L34) ### Pydantic Schemas and Data Models Request validation and response serialization rely on explicit Pydantic models across all routers. Submodules enforce specific payload contracts for entity grouping, API key lifecycle management, and telemetry logging. ```python class Entity(BaseModel): id: str type: EntityType total_memories: int created_at: Optional[datetime] = None updated_at: Optional[datetime] = None ``` Sources: [server/routers/entities.py:20-26](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L20-L26) ```python class CreateKeyRequest(BaseModel): label: str class CreateKeyResponse(BaseModel): id: str key: str label: str key_prefix: str created_at: datetime class KeyListItem(BaseModel): id: str label: str key_prefix: str created_at: datetime last_used_at: datetime | None ``` Sources: [server/routers/api_keys.py:17-35](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L17-L35) ```typescript export interface ApiRequestLog { id: string; created_at: string; method: string; path: string; status_code: number; latency_ms: number; auth_type: string; } export type EntityType = "user" | "agent" | "run"; export interface Entity { id: string; type: EntityType; total_memories: number; created_at: string | null; updated_at: string | null; } ``` Sources: [server/dashboard/src/types/api.ts:26-44](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L26-L44) ## Memory Operations and Data Schemas ### Endpoint Routing and Payload Structures Memory management endpoints provide full CRUD capabilities alongside specialized sub-routes for inspecting history, configuring providers, resetting data stores, and generating system instructions. The base path for memory operations is defined at `/memories`, with dynamic sub-routes supporting resource identification via unique memory identifiers and entity categorization. ```typescript export const MEMORY_ENDPOINTS = { BASE: "/memories", BY_ID: (memoryId: string) => `/memories/${memoryId}`, HISTORY: (memoryId: string) => `/memories/${memoryId}/history`, CONFIGURE: "/configure", CONFIGURE_PROVIDERS: "/configure/providers", RESET: "/reset", GENERATE_INSTRUCTIONS: "/generate-instructions", } as const; ``` Sources: [server/dashboard/src/utils/api-endpoints.ts:11-19](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L11-L19) The `Memory` data structure standardizes serialization for both single-item retrievals and collection responses. Each memory object exposes an unique identifier, the memory text payload, optional scoping metadata for user or agent associations, and timestamps tracking creation and modification events. ```typescript export interface Memory { id: string; memory: string; user_id?: string; agent_id?: string; created_at?: string; updated_at?: string; } ``` Sources: [server/dashboard/src/types/api.ts:1-8](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L1-L8) | Endpoint Path | Parameter / Payload | Description | | :--- | :--- | :--- | | `/memories` | POST / GET | Create a new memory record or list stored memories across scoped contexts | | `/memories/{memoryId}` | GET / PUT / DELETE | Retrieve, update, or delete a specific memory entry by its unique identifier | | `/memories/{memoryId}/history` | GET | Fetch the complete modification history log for a designated memory record | | `/configure` | GET / POST | Inspect or update global system configuration settings | | `/configure/providers` | GET / POST | Manage external LLM and vector store provider integrations | | `/reset` | POST | Purge system storage and reset persistent memory stores | | `/generate-instructions` | POST | Automatically synthesize agent instruction sets from recorded memory contexts | Sources: [server/dashboard/src/utils/api-endpoints.ts:11-19](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L11-L19), [server/dashboard/src/types/api.ts:1-8](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L1-L8) > [!NOTE] > Scoping identifiers such as `user_id` and `agent_id` are optional on the base `Memory` interface, allowing global memory creation when neither parameter is provided during ingestion. > Sources: [server/dashboard/src/types/api.ts:1-8](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L1-L8) ## Entity Browsing and Management ### Entity Routing and Schemas The entity routing module exposes endpoints prefixed at `/entities` under the `entities` router tag to inspect, aggregate, and purge vector store payloads by their scoping fields. Authentication is enforced via dependency injection, requiring standard verification for listing operations and administrative privileges for deletion requests. ```python router = APIRouter(prefix="/entities", tags=["entities"]) SCAN_LIMIT = 10_000 EntityType = Literal["user", "agent", "run"] TYPE_TO_FIELD: dict[EntityType, str] = {"user": "user_id", "agent": "agent_id", "run": "run_id"} ``` Sources: [server/routers/entities.py:12-18](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L12-L18) Entity categories are defined by the `EntityType` literal union supporting `"user"`, `"agent"`, and `"run"` scopes. The `TYPE_TO_FIELD` dictionary maps each entity type to its corresponding payload metadata key: `"user"` maps to `"user_id"`, `"agent"` maps to `"agent_id"`, and `"run"` maps to `"run_id"`. ```typescript export type EntityType = "user" | "agent" | "run"; export interface Entity { id: string; type: EntityType; total_memories: number; created_at: string | null; updated_at: string | null; } ``` Sources: [server/dashboard/src/types/api.ts:36-44](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L36-L44) The Pydantic `Entity` model and its TypeScript dashboard equivalent structure the serialized representation returned to clients. Each entity record contains a unique string identifier, its category type, the total memory count aggregated across matching payloads, and ISO-8601 timestamps marking creation and update events. ```python class Entity(BaseModel): id: str type: EntityType total_memories: int created_at: Optional[datetime] = None updated_at: Optional[datetime] = None ``` Sources: [server/routers/entities.py:20-26](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L20-L26) | Endpoint Path | Method | Auth Dependency | Description | | :--- | :--- | :--- | :--- | | `/entities` | GET | `verify_auth` | Scan vector store payloads and return aggregated entity summaries | | `/entities/{entity_type}/{entity_id}` | DELETE | `require_admin` | Purge all memories linked to the specified entity type and identifier | Sources: [server/routers/entities.py:43-44](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L43-L44), [server/routers/entities.py:70-71](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L70-L71), [server/dashboard/src/utils/api-endpoints.ts:30-33](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L30-L33) > [!NOTE] > The `list_entities` endpoint scans vector store payloads up to a hardcoded `SCAN_LIMIT` of 10,000 records, building dynamic aggregation buckets across user, agent, and run identifier fields. > Sources: [server/routers/entities.py:14-15](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L14-L15), [server/routers/entities.py:45-47](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L45-L47) ### Aggregation and Deletion Logic ```python def _iter_payloads() -> list[dict[str, Any]]: results = get_memory_instance().vector_store.list(top_k=SCAN_LIMIT) rows = results[0] if results and isinstance(results, list) and isinstance(results[0], list) else results or [] return [getattr(row, "payload", None) or {} for row in rows] ``` Sources: [server/routers/entities.py:28-32](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L28-L32) ```python for payload in _iter_payloads(): created = _parse_timestamp(payload.get("created_at")) updated = _parse_timestamp(payload.get("updated_at")) or created for entity_type, field in TYPE_TO_FIELD.items(): value = payload.get(field) if not value: continue bucket = buckets[(entity_type, str(value))] bucket["total_memories"] += 1 if created and (bucket["created_at"] is None or created < bucket["created_at"]): bucket["created_at"] = created if updated and (bucket["updated_at"] is None or updated > bucket["updated_at"]): bucket["updated_at"] = updated return [ Entity(id=entity_id, type=entity_type, **data) for (entity_type, entity_id), data in sorted(buckets.items(), key=lambda item: (item[0][0], item[0][1])) ] ``` Sources: [server/routers/entities.py:49-67](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L49-L67) ```python @router.delete("/{entity_type}/{entity_id}", response_model=MessageResponse) def delete_entity(entity_type: EntityType, entity_id: str, _auth=Depends(require_admin)): try: get_memory_instance().delete_all(**{TYPE_TO_FIELD[entity_type]: entity_id}) except Exception: raise upstream_error() return MessageResponse(message="Entity deleted") ``` Sources: [server/routers/entities.py:70-76](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L70-L76) > [!WARNING] > Deleting an entity via `delete_entity` invokes `get_memory_instance().delete_all(...)` filtered by the mapped field name, permanently removing every memory associated with that identifier across the underlying data store. > Sources: [server/routers/entities.py:70-73](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/entities.py#L70-L73) ## API Key Lifecycle and Rotation ### Key Management Endpoints and Schemas The API key router manages administrative credential generation, prefix enumeration, and revocation under the `/api-keys` route prefix with the `api-keys` tag. All operations require authenticated user sessions via dependency injection. ```python router = APIRouter(prefix="/api-keys", tags=["api-keys"]) class CreateKeyRequest(BaseModel): label: str class CreateKeyResponse(BaseModel): id: str key: str label: str key_prefix: str created_at: datetime class KeyListItem(BaseModel): id: str label: str key_prefix: str created_at: datetime last_used_at: datetime | None model_config = {"from_attributes": True} ``` Sources: [server/routers/api_keys.py:14-37](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L14-L37) | Endpoint Path | Method | Status Code | Description | | :--- | :--- | :--- | :--- | | `/api-keys` | GET | `200` | List all active API keys created by the authenticated user | | `/api-keys` | POST | `201` | Generate and persist a new API key with a given label | | `/api-keys/{key_id}` | DELETE | `200` | Revoke an existing API key by marking its revocation timestamp | Sources: [server/routers/api_keys.py:39-40](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L39-L40), [server/routers/api_keys.py:62-63](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L62-L63), [server/routers/api_keys.py:79-80](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L79-L80) > [!NOTE] > The `list_keys` endpoint filters out revoked API keys where `revoked_at` is not null, ordering active credentials by creation date in descending order. > Sources: [server/routers/api_keys.py:41-49](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L41-L49) ### Key Generation and Revocation Logic ```python @router.post("", response_model=CreateKeyResponse, status_code=201) def create_key(body: CreateKeyRequest, user: User = Depends(require_auth), db: Session = Depends(get_db)): full_key, prefix, key_hash = generate_api_key() api_key = APIKey(key_prefix=prefix, key_hash=key_hash, label=body.label, created_by=user.id) db.add(api_key) db.commit() db.refresh(api_key) return CreateKeyResponse( id=str(api_key.id), key=full_key, label=api_key.label, key_prefix=prefix, created_at=api_key.created_at, ) ``` Sources: [server/routers/api_keys.py:62-76](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L62-L76) ```python @router.delete("/{key_id}", response_model=MessageResponse) def revoke_key(key_id: str, user: User = Depends(require_auth), db: Session = Depends(get_db)): try: key_uuid = uuid.UUID(key_id) except (TypeError, ValueError): raise HTTPException(status_code=404, detail="API key not found.") api_key = db.get(APIKey, key_uuid) if api_key is None or api_key.created_by != user.id: raise HTTPException(status_code=404, detail="API key not found.") if api_key.revoked_at is not None: raise HTTPException(status_code=400, detail="API key is already revoked.") api_key.revoked_at = datetime.now(timezone.utc) db.commit() return MessageResponse(message="API key revoked.") ``` Sources: [server/routers/api_keys.py:79-93](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L79-L93) > [!WARNING] > The `revoke_key` endpoint validates that the target identifier parses as a valid UUID and that the key belongs to the requesting user before setting `revoked_at` to the current UTC time. Attempting to revoke an already revoked key raises a `400` status error. > Sources: [server/routers/api_keys.py:81-91](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/routers/api_keys.py#L81-L91) ## Telemetry and Request Logging Endpoints ### Request Log Aggregation and Schemas Request logging endpoints capture runtime telemetry across server operations. The dashboard client references these endpoints through the `REQUEST_ENDPOINTS` utility mapping. ```typescript export const REQUEST_ENDPOINTS = { BASE: "/requests", } as const; ``` Sources: [server/dashboard/src/utils/api-endpoints.ts:26-28](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L26-L28) Telemetry data structures are represented in the frontend via the `ApiRequestLog` interface, capturing audit metadata including execution path, HTTP method, response status, processing latency, and authentication scheme. ```typescript export interface ApiRequestLog { id: string; created_at: string; method: string; path: string; status_code: number; latency_ms: number; auth_type: string; } ``` Sources: [server/dashboard/src/types/api.ts:26-34](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L26-L34) | Field Name | Type | Description | | :--- | :--- | :--- | | `id` | `string` | Unique identifier for the recorded request log entry | | `created_at` | `string` | Timestamp indicating when the request was processed | | `method` | `string` | HTTP request method (e.g. `GET`, `POST`, `DELETE`) | | `path` | `string` | Request path or route target | | `status_code` | `number` | HTTP response status code returned by the server | | `latency_ms` | `number` | Processing duration measured in milliseconds | | `auth_type` | `string` | Authentication mechanism utilized for the request | Sources: [server/dashboard/src/types/api.ts:27-33](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L27-L33) > [!NOTE] > Request logs aggregate transactional metrics across all incoming API calls, enabling administrative audit trails and performance monitoring within the [dashboard views](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/server-dashboard/dashboard-views). > Sources: [server/dashboard/src/types/api.ts:26-34](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/types/api.ts#L26-L34) ## Health Inspection and System Status ### Setup Status and Health Probes The server provides endpoints to inspect application readiness, configuration state, and setup initialization requirements. The dashboard client accesses setup verification via authentication endpoint paths mapped in the utility configuration. ```typescript export const AUTH_ENDPOINTS = { SETUP_STATUS: "/auth/setup-status", REGISTER: "/auth/register", LOGIN: "/auth/login", REFRESH: "/auth/refresh", ME: "/auth/me", CHANGE_PASSWORD: "/auth/change-password", ONBOARDING_COMPLETE: "/auth/onboarding-complete", } as const; ``` Sources: [server/dashboard/src/utils/api-endpoints.ts:1-9](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L1-L9) | Endpoint Constant | Path Value | Description | | :--- | :--- | :--- | | `SETUP_STATUS` | `/auth/setup-status` | Inspects whether the server requires initial admin user registration | | `REGISTER` | `/auth/register` | Registers the initial administrator account during setup | | `LOGIN` | `/auth/login` | Authenticates existing users and issues access credentials | | `REFRESH` | `/auth/refresh` | Refreshes authentication tokens | | `ME` | `/auth/me` | Retrieves profile details for the currently authenticated user | | `CHANGE_PASSWORD` | `/auth/change-password` | Updates user credentials | | `ONBOARDING_COMPLETE` | `/auth/onboarding-complete` | Marks initial onboarding flows as complete | Sources: [server/dashboard/src/utils/api-endpoints.ts:2-8](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L2-L8) > [!NOTE] > The `/auth/setup-status` endpoint allows unauthenticated clients to determine whether the server has completed its initial administrator provisioning, guiding the frontend [Dashboard Architecture](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/server-dashboard/dashboard-architecture) setup wizard. > Sources: [server/dashboard/src/utils/api-endpoints.ts:2](https://github.com/blade47/mem0/blob/b7ad69afda6b6ed030347c66d48a13e4de9dec08/server/dashboard/src/utils/api-endpoints.ts#L2) ## Related - [FastAPI Application](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/server-dashboard/fastapi-application) - [Python Client SDK](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/technical/python-core/python-client-sdk) ## Sitemap See the full [sitemap](https://www.doc0.dev/docs/faa36707-7c28-4f69-a18f-700ff61c704e/llms.txt) for all pages in this wiki.