Skip to main content
Manage pipeline configurations through CRUD operations.

Get a Pipeline

Parameters: Example:
Response: 200 OK with the full PipelineConfig JSON.

List All Pipelines

Example:
Response: 200 OK with an array of all PipelineConfig objects.

Create or Update a Pipeline

Body: Full PipelineConfig JSON (see Pipeline Configuration). Parameters: Example:
Response: 200 OK Validation: The configuration is validated before saving. Invalid configurations return 500 with error details. See Pipeline Configuration for all constraints.

Delete a Pipeline

Parameters: Examples:
Response: 200 OK

AI Schema Generation

To generate a pipeline configuration automatically from an uploaded file, see the AI Schema Generation API.

Authentication

If useApiKeys is enabled, all requests must include the x-api-key header:
API keys are stored in Vault under {environment}/api-keys (oss/api-keys on a default install). secrets.apiKeysSecretName in application.yaml tells the validator where to read them and should point at that same path — the Keys UI and multi-tenant resolution always write to {environment}/api-keys.