fileKey you pass to import create, and prints the headers, a sample preview, and TalkValue’s suggested column mapping. Required target fields the file cannot satisfy come back under missingRequired so you can fix the file before running the full import.
Synopsis
Options
| Flag | Type | Description |
|---|---|---|
--file <path> | string (required) | Path to the CSV file on disk. Read locally, uploaded as multipart/form-data. Permission and “file not found” errors surface as usage errors with no upload attempt. |
Examples
1. Inspect a file before importing
fileKey, the row count, headers, the first few rows as preview, and the suggested column mappings.
2. Pipe the mapping into a script
csvIndex:targetField pair per line, ready to feed into import create --mapping. Capture .data.fileKey from the same response and you have both pieces the create step needs.
3. Halt the pipeline when required fields are missing
jq -e exits non-zero if missingRequired has entries, so the surrounding shell can fail loudly instead of forwarding a broken file to import create.
Response
fileKey is the only field you must keep. It is the handle import create requires. Each entry in columnMappings carries the CSV column’s index and header alongside the server’s suggestedField guess plus a confidence score. Pass csvIndex:suggestedField to import create --mapping, overriding any guess you disagree with.
See also
import create. The next step that consumes thefileKeyand mapping.- Column mapping. The full list of valid target fields.
- Recipe: CSV import. Analyze, create, status in one script.
