Official templates are platform-maintained workflows. Discover them from the active environment instead of relying on a static list:
The schema response is authoritative for field keys, labels, required inputs, accepted values, and the current template version.
Workbook flow
validate-file and precheck-file do not create a run. submit-file does.
After submission:
Programmatic JSON or JSONL flow
Use the staged commands with the same unchanged input file:
The file may be a JSON array or JSONL. The CLI reads the template schema and maps accepted field keys or workbook header labels before validation.
Do not skip from validate to execute. If the file changes after precheck or confirmation, validate and precheck it again, show the new estimate, and obtain a new confirmation.
run execute also accepts --callback-url. Treat callback endpoints as sensitive integration configuration and use HTTPS.
Legacy backfill
Prefer the server-generated result workbook. Use local backfill only when maintaining an older workflow:
See Runs for monitoring and Money units for the confirmation contract. 
