← Files GoodMemARCHIVED FILE
skills/goodmem-sdk/references/typescript/models/MemoryCreateFromPathRequest.md
1.8 KB · Oct 2, 2026 · 00:24 UTC
<!-- sdk-ref package=@pairsystems/goodmem registry=npm version=0.1.6 -->
# MemoryCreateFromPathRequest
```ts
export type MemoryCreateFromPathRequest = Prettify<MemoryUploadMetadata & {
path: string | URL;
contentType?: string | null;
filename?: string | null;
}>;
```
Effective request fields (including inherited fields and overrides):
- `chunkingConfig` (`ChunkingConfiguration | null | undefined`, optional): Chunking strategy for this memory (if not provided, uses space default)
- `contentType` (`string | null | undefined`, optional):
- `extractPageImages` (`boolean | null | undefined`, optional): Optional hint to extract page images for eligible document types (for example, PDFs)
- `filename` (`string | null | undefined`, optional):
- `memoryId` (`string | null | undefined`, optional): Optional client-provided UUID for the memory. If omitted, the server generates one. Returns ALREADY_EXISTS if the ID is already in use.
- `metadata` (`Record<string, unknown> | null | undefined`, optional): Additional metadata for the memory. A top-level textual title is an optional document-title hint for embedding providers that support one; blank or non-string titles are ignored. Later metadata edits do not automatically re-embed existing chunks.
- `originalContentRef` (`string | null | undefined`, optional): Reference to external content location
- `path` (`string | URL`, required):
- `spaceId` (`string`, required): ID of the space where this memory will be stored
Helper definitions for the constraints above (kept here to avoid extra page reads):
```ts
export type Prettify<T> = {
[K in keyof T]: T[K];
} & {};
```
[TypeScript](../../typescript.md)
Related types — open only those used by your request:
- [ChunkingConfiguration](ChunkingConfiguration.md)
- [MemoryUploadMetadata](MemoryUploadMetadata.md)
SHA-256: d9d0466c16be511d6a1bf29ebc5d9567f83150213b8eb3f09672435d1dca1205