Feature Request: Service API support for Pipeline Knowledge Base document operations #21896

Open
opened 2026-02-21 20:14:46 -05:00 by yindo · 2 comments
Owner

Originally created by @nitpcy on GitHub (Jan 26, 2026).

Originally assigned to: @fatelei on GitHub.

Current Situation

The Service API currently doesn't support document creation and update operations for Pipeline Knowledge Bases (RAG Pipeline mode), though these operations are available for Vendor Knowledge Bases.

Requested Features

Would it be possible to add the following capabilities to Service API for Pipeline Knowledge Bases:

  1. Create documents by text
  2. Update documents by text
  3. Create documents by file
  4. Update documents by file
  5. List and query documents
  6. Delete documents

Use Case

This would enable programmatic document management for Pipeline Knowledge Bases, similar to what's already available for Vendor Knowledge Bases.

Related

Originally created by @nitpcy on GitHub (Jan 26, 2026). Originally assigned to: @fatelei on GitHub. ### Current Situation The Service API currently doesn't support document creation and update operations for Pipeline Knowledge Bases (RAG Pipeline mode), though these operations are available for Vendor Knowledge Bases. ### Requested Features Would it be possible to add the following capabilities to Service API for Pipeline Knowledge Bases: 1. Create documents by text 2. Update documents by text 3. Create documents by file 4. Update documents by file 5. List and query documents 6. Delete documents ### Use Case This would enable programmatic document management for Pipeline Knowledge Bases, similar to what's already available for Vendor Knowledge Bases. ### Related - Issue #30203
yindo added the 💪 enhancement label 2026-02-21 20:14:46 -05:00
Author
Owner

@QuantumGhost commented on GitHub (Jan 26, 2026):

Pipeline Knowledge Bases are not a separate type of knowledge bases. Rather, they are standard knowledge bases enhanced by the Knowledge Pipeline for document indexing.

For point 5 and 6, you should use the existing Knowledge Base APIs. Please refer to the following:

As for APIs for creating / updating documents using the Knowledge Pipeline, we'll evaluate the feature request.

@QuantumGhost commented on GitHub (Jan 26, 2026): Pipeline Knowledge Bases are not a separate type of knowledge bases. Rather, they are standard knowledge bases enhanced by the Knowledge Pipeline for document indexing. For point 5 and 6, you should use the existing Knowledge Base APIs. Please refer to the following: - [Get the Document List of a Knowledge Base](https://docs.dify.ai/api-reference/documents/get-the-document-list-of-a-knowledge-base) - [Get document detail](https://docs.dify.ai/api-reference/documents/get-document-detail) - [Delete Document](https://docs.dify.ai/api-reference/documents/delete-a-document) As for APIs for creating / updating documents using the Knowledge Pipeline, we'll evaluate the feature request.
Author
Owner

@QuantumGhost commented on GitHub (Jan 26, 2026):

Related Discussion: https://github.com/langgenius/dify/discussions/31583

@QuantumGhost commented on GitHub (Jan 26, 2026): Related Discussion: https://github.com/langgenius/dify/discussions/31583
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21896