> ## 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 datasources within a knowledge base. Returns metadata, status, and configuration for each datasource in the specified knowledge base. # List all datasources ## OpenAPI ````yaml get /v2/knowledge/{knowledge_id}/datasources 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: - name: Guardrail Rules - name: Policies - name: Routing Rules - name: Files description: File upload and retrieval operations. - name: FilesService - name: Projects description: Projects organize resources within a workspace - name: ProjectsService - name: Skills description: >- Skills are modular instructions you can use to codify processes and conventions - name: SkillsService - name: Responses - description: >- Run agents on a cadence — cron, interval, or one-off. Minimum firing interval is 1 hour. name: Agent Schedules - 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. - name: ReportingService description: |- ReportingService exposes a single QueryReport RPC that maps allowlisted analytics payloads onto safe rollup queries. Callers never send SQL; the backend picks the rollup family and grain from the metric catalogue, the requested range, and the requested grouping. externalDocs: url: https://docs.orq.ai description: orq.ai Documentation paths: /v2/knowledge/{knowledge_id}/datasources: get: tags: - Knowledge Bases summary: List all datasources operationId: ListDatasources parameters: - schema: type: string description: Unique identifier of the knowledge base required: true description: Unique identifier of the knowledge base name: knowledge_id in: path - 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 description: Search query to find datasources by name. required: false description: Search query to find datasources by name. name: q in: query - schema: type: number minimum: 1 maximum: 50 default: 50 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: anyOf: - type: array items: type: string example: - completed - failed - type: string example: completed description: Filter datasources by status. required: false description: Filter datasources by status. name: status in: query responses: '200': description: Datasources successfully retrieved content: application/json: schema: type: object properties: object: type: string enum: - list data: type: array items: type: object properties: _id: type: string format: ulid pattern: ^[0-9A-HJKMNP-TV-Z]{26}$ default: 01KRM5REJME30D2KCXQ2E5QXQT readOnly: true description: The unique identifier of the data source display_name: type: string description: >- The display name of the datasource. Normally the name of the uploaded file description: type: string description: The description of the knowledge base status: type: string enum: - pending - processing - completed - failed - queued file_id: type: - string - 'null' description: >- The unique identifier of the file used to create the datasource. created: type: string description: The date and time the datasource was created updated: type: string description: The date and time the datasource was updated created_by_id: type: - string - 'null' format: uuid pattern: >- ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$ readOnly: true description: The user ID of the creator of the knowledge base update_by_id: type: - string - 'null' format: uuid pattern: >- ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$ readOnly: true description: >- The user ID of the last user who updated the knowledge base knowledge_id: type: string description: The unique identifier of the knowledge base chunks_count: type: number description: The number of chunks in the datasource required: - display_name - status - created - updated - knowledge_id - chunks_count has_more: type: boolean required: - object - data - has_more components: securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ````