A configuration version (Config) saves which steps to run and how each step works. For example, version 1 may extract an invoice number and total, while version 2 also extracts the invoice date. Saving version 2 keeps version 1 available.
Save a new version
Start from the complete two-step settings. Change the extraction fields, give the version a new name, and set is_default to False while testing. Send the full steps list when creating the new version; this does not edit the old version.
Python examples use client and the IDs saved in the quickstart. cURL examples use UPSTAGE_API_KEY, WORKFLOW_ID, CONFIG_ID, FILE_ID, and JOB_ID from the same flow; set the IDs needed for each operation. Preserve node_id when it is present: it identifies the same processing step across versions.
Test without changing the default
Use the new candidate_id as config_id in the execution request. Other requests that omit config_id still use the default version. Compare the result with the original document before selecting a default.
Select a default or return to an older version
The default is used only when config_id is omitted. It is not necessarily the most recently created version. To go back, send the same request with a previous Config ID. Earlier jobs retain the version used when they ran.
Find and manage versions
Use the returned cfg_... ID in requests; the displayed version sequence (external_id) is not a Config ID. Existing versions allow name/default changes, not step edits. Deleting the default version clears the workflowโs default configuration, so subsequent execution requests without config_id fail. To keep those requests working, select another default before deleting the current default. See Config operations and Connecting steps.
In cURL, the candidate version ID is stored as CANDIDATE_ID. Use it in place of CONFIG_ID when testing.