Skip to main content
POST
Submit Data Job
Create a new data job. The job_type field determines the workflow:
  • principle_files — generates a QA pair dataset for instruction fine-tuning
  • context_grounded_files — generates context-grounded training data from uploaded documents
  • context_grounded_vector_db — generates context-grounded training data using an existing vector database
Newly created jobs have no files attached. Use POST /v1/flow/data-jobs/{id}/add-files to attach uploaded file IDs after creation. For the complete workflow, see Create instruction fine-tuning data or Create context-grounded fine-tuning data.

Authorizations

Authorization
string
header
required

Your Seekr API key, sent in the Authorization header with no 'Bearer' prefix.

Body

application/json
name
string
required
Required string length: 1 - 255
job_type
enum<string>
required

Valid job types for data jobs.

Available options:
principle_files,
context_grounded_files,
context_grounded_vector_db
system_prompt
string | null

System prompt included with every conversation in the generated dataset. It becomes part of the training data the fine-tuned model learns from, unlike instructions, which only shapes how the dataset is generated. If omitted, one is generated for you from instructions and the source documents.

Minimum string length: 1
instructions
string | null

Natural-language description of the task the generated dataset should support. Alignment uses it to shape the examples it produces, such as the topics and the kinds of questions a fine-tuned model should be able to handle.

Minimum string length: 1
vector_database_id
string | null

Response

Resource created

Lightweight response for list view performance.

id
string
required
user_id
string
required
name
string
required
job_type
string
required
alignment_job_id
string | null
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
status
required

Status values that exist BEFORE an alignment job is linked. Once linked, the real status comes from AlignmentJobStatus directly — see DataJobResponse.status's union type and derive_data_job_status.

Available options:
file_processing,
needs_review,
ready_to_start
origin_data_job_id
string | null
deleted
boolean
default:false
status_message
string | null
system_prompt
string | null
system_prompt_updated_at
string<date-time> | null
instructions
string | null
instructions_updated_at
string<date-time> | null
resolved_instructions
string | null
vector_database_id
string | null
Last modified on July 31, 2026