Execute the full knowledge pipeline for a knowledge base. Supports both streaming and blocking response modes.
API Key authentication. For all API requests, include your API Key in the Authorization HTTP Header, prefixed with Bearer. Example: Authorization: Bearer {API_KEY}. Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.
Knowledge base ID.
Input variables for the pipeline.
Type of the datasource.
online_document, local_file, website_crawl, online_drive List of datasource information objects for the pipeline to process.
ID of the node to start pipeline execution from.
Whether to run the published or draft version of the pipeline. true runs the published version, false runs the draft.
Response mode for the pipeline execution. streaming returns a Server-Sent Events stream, blocking waits and returns the complete result.
streaming, blocking Pipeline execution result. Format depends on response_mode: streaming returns a text/event-stream, blocking returns a JSON object.
Server-Sent Events stream containing pipeline execution progress and results. Returned when response_mode is streaming.