Uploads and datasets

Attach tabular source data and reference it with dataset and pick constructs. Uploaded files can provide dataset table rows or values selected through pick(@part.column). Declare the source in the recipe, then include matching file parts when validating or generating through an API client. Uploaded contents are user-provided input. GBDDL validation and pricing are shared across Chef, the HTTP API and MCP. Consult the recipe language, output formats, and credit model for the supported syntax and behavior.

File formats and API submission

Uploads accept UTF-8 CSV, TSV, JSONL objects or plain one-value-per-line lists. Format detection uses content; delimited files need headers. A plain list exposes a column named value.

For validation, preview or job creation, send multipart/form-data with exactly one text field named recipe, plus the source files. The uploaded filename identifies the part referenced by @part in the recipe; form field names do not select it. Keep the required input_format=gbddl or input_format=json query parameter. Submit the files again for each request that uses them. Uploaded job sources are retained for processing, so use synthetic input rather than personal data.