> ## Documentation Index > Fetch the complete documentation index at: https://docs.orq.ai/llms.txt > Use this file to discover all available pages before exploring further. # List all documents for a memory > Retrieves a paginated list of documents associated with a specific memory. ## OpenAPI ````yaml get /v2/memory-stores/{memory_store_key}/memories/{memory_entity_id}/documents openapi: 3.1.0 info: title: orq.ai API version: '2.0' description: orq.ai API documentation servers: - url: https://api.orq.ai security: - ApiKey: [] tags: - description: List models available through the AI Router. name: Models - name: Guardrail Rules - name: Policies - name: Routing Rules - name: API keys description: >- API keys authenticate programmatic access to the workspace. The unified key model exposes opaque tokens, per-domain access grants, and budget / rate-limit constraints (see ADR 0001 and ADR 0002). - name: Budgets description: >- Budgets govern spend, token usage, and request rate across six scopes: workspace, project, identity, api-key, provider, and model. A budget is hierarchical and defense-in-depth — every applicable budget is a hard gate, and the most restrictive one wins per dimension (see ADR 0007). - name: Documentation description: >- Search the orq.ai documentation. Proxies the workspace's query to the hosted docs search index. - name: Files description: File upload and retrieval operations. - name: Identities description: >- Identities represent end users from your system for usage and engagement tracking. - name: Projects description: Projects organize resources within a workspace - name: Skills description: >- Skills are modular instructions you can use to codify processes and conventions - name: Responses - description: >- Run agents on a cadence — cron, interval, or one-off. Minimum firing interval is 1 hour. name: Agent Schedules - name: Embeddings - name: Reporting description: >- GenAI reporting API over canonical analytics rollups. Accepts a metric name, time range, grain, group-by, and filters; returns a typed time series and optional totals. externalDocs: url: https://docs.orq.ai description: orq.ai Documentation paths: /v2/memory-stores/{memory_store_key}/memories/{memory_entity_id}/documents: get: tags: - Memory Stores summary: List all documents for a memory description: >- Retrieves a paginated list of documents associated with a specific memory. operationId: GetAllMemoryDocuments parameters: - schema: type: string description: The unique key identifier of the memory store required: true description: The unique key identifier of the memory store name: memory_store_key in: path - schema: type: string description: The unique identifier of the memory required: true description: The unique identifier of the memory name: memory_entity_id in: path - schema: type: integer minimum: 1 maximum: 200 default: 10 description: >- A limit on the number of objects to be returned. Limit can range between 1 and 50, and the default is 10 required: false description: >- A limit on the number of objects to be returned. Limit can range between 1 and 50, and the default is 10 name: limit in: query - schema: type: string description: >- A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, ending with `01JJ1HDHN79XAS7A01WB3HYSDB`, your subsequent call can include `after=01JJ1HDHN79XAS7A01WB3HYSDB` in order to fetch the next page of the list. required: false description: >- A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, ending with `01JJ1HDHN79XAS7A01WB3HYSDB`, your subsequent call can include `after=01JJ1HDHN79XAS7A01WB3HYSDB` in order to fetch the next page of the list. name: starting_after in: query - schema: type: string description: >- A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, starting with `01JJ1HDHN79XAS7A01WB3HYSDB`, your subsequent call can include `before=01JJ1HDHN79XAS7A01WB3HYSDB` in order to fetch the previous page of the list. required: false description: >- A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, starting with `01JJ1HDHN79XAS7A01WB3HYSDB`, your subsequent call can include `before=01JJ1HDHN79XAS7A01WB3HYSDB` in order to fetch the previous page of the list. name: ending_before in: query - schema: type: string format: date-time description: Filter documents updated after this ISO datetime required: false description: Filter documents updated after this ISO datetime name: updated_after in: query - schema: type: string format: date-time description: Filter documents updated before this ISO datetime required: false description: Filter documents updated before this ISO datetime name: updated_before in: query responses: '200': description: Successfully retrieved the list of memory documents. content: application/json: schema: type: object properties: object: type: string enum: - list data: type: array items: type: object properties: _id: type: string memory_id: type: string store_id: type: string text: type: string minLength: 1 description: >- The content of the memory document (whitespace trimmed). created: type: string updated: type: string created_by_id: type: - string - 'null' updated_by_id: type: - string - 'null' workspace_id: type: string metadata: type: object additionalProperties: type: string default: {} description: >- Flexible key-value pairs for custom filtering and categorization. Clients can add arbitrary string metadata to enable future filtering of memory documents based on their specific needs (e.g., document type, source, topic, relevance score, or any custom taxonomy). required: - _id - memory_id - store_id - text - created - updated - workspace_id has_more: type: boolean required: - object - data - has_more '401': description: Unauthorized - Bearer token is missing or invalid '403': description: Forbidden - Insufficient permissions to access memory documents '404': description: Memory not found components: securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ````