The context_grounded_files and context_grounded_vector_db job types stop working on November 9, 2026. You can keep using them until then. For new projects, choose another fine-tuning method.
# List only principle_files jobs, most recent firstjobs = client.data_jobs.list( job_type="principle_files", sort_by="created_at", sort_order="desc", limit=10,)for job in jobs.data: print(job.id, job.name, job.status)
Endpoint:GET /v1/flow/data-jobs/{id}Returns the full job detail including ingestion jobs, file records, timeline events, and alignment status. See Monitor ingestion for a field-by-field reference.
Endpoint:POST /v1/flow/data-jobs/{id}/cloneCreate a new, editable data job pre-populated from an existing one. The clone copies the source job’s configuration and starts as a fresh job that you can adjust before starting alignment. Give the clone a new name, or omit name to reuse the source job’s name.
Endpoint:PATCH /v1/flow/data-jobs/{id}Update the job name, instructions, system prompt, or vector database ID without recreating the job.
data_job = client.data_jobs.update( "dj-1234567890", name="Customer support refresh v2", instructions="Cover airline escalation policies in the generated dataset.", system_prompt="You are an airline support expert. Always cite the policy section.",)print("Updated name:", data_job.name)
Editable fields:
Field
Notes
name
Keep under 255 characters.
instructions
Natural-language instructions that guide alignment toward the intended task.
system_prompt
Required for principle_files jobs before starting. Immediately overwrites the stored value.
vector_database_id
Required for context_grounded_vector_db jobs before starting.
Once alignment starts, job inputs are locked. Attempting to update a running job returns 409 Conflict.
Endpoint:POST /v1/flow/data-jobs/{id}/cancelCancels the alignment run associated with the data job. Only applies when alignment is in pending, queued, or running state.
