Skip to main content

Upload a File

Upload a data file for processing by a configured pipeline.
Parameters: Behavior:
  • Compressed files (.zip, .gz, .tar, .jar): Extracted in-process. For a CSV pipeline with several files in the archive, the files are concatenated (headers on files 2+ skipped) and submitted as one batch job; otherwise each extracted file is submitted as its own job
  • Uncompressed files: Processed immediately in-memory
  • Schema evolution: If a CSV file contains new columns not in the pipeline schema, they are automatically added (as string type) and the destination table is altered. See Schema Evolution.
Example:
Response: 200 OK with the pipeline token (for uncompressed files):
For compressed files, the response is 200 OK with the single pipeline token of the batch job (CSV batch mode, or a single-file archive), or the plain-text summary N file(s) submitted when each extracted file was submitted as its own job.

Generate Pipeline Schema

Upload a CSV file to automatically infer the schema and generate a partial pipeline configuration.
Parameters: Example:
Response: 200 OK with a partial PipelineConfig JSON:
Inferred types: boolean, int, bigint, float, double, string, date, timestamp Note: For CSV files, the AI analyzes the content and infers types. For JSON and XML files, a default config is generated with a single _json or _xml string field. When allStrings is true, all fields are set to string (used by the MCP server for reliable ingestion). The destination block carries DATABASE_NAME / SCHEMA_NAME / TABLE_NAME placeholders; replace them before registering the config with POST /pipeline.

Profile Data

Upload a data file for AI-powered profiling — get summary statistics, quality issues, and suggested validation rules.
Parameters: Example:
Response: 200 OK with a JSON profile including summary statistics, quality issues, recommendations, and suggested data quality rules. See AI Data Profiling for the full response format.