Skip to main content
POST
Submit Data Job
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.
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

Name of the data job.

Required string length: 1 - 256
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.

Required string length: 1 - 32768
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.

Required string length: 1 - 32768
vector_database_id
string | null

ID of the vector database the data job draws on.

Response

Resource created

Lightweight response for list view performance.

id
string
required

ID of the data job.

user_id
string
required

ID of the user who owns the data job.

name
string
required

Name of the data job.

job_type
string
required

Type of the data job, such as principle_files or context_grounded_files.

alignment_job_id
string | null
required

ID of the alignment job linked to the data job. null until one is linked.

created_at
string<date-time>
required

Time the data job was created, in ISO 8601 format.

updated_at
string<date-time>
required

Time the data job was last updated, in ISO 8601 format.

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

ID of the data job this job was cloned from. null unless the job was created by cloning.

deleted
boolean
default:false

If true, the data job was deleted.

status_message
string | null

Human-readable description of the job's current state.

system_prompt
string | null

System prompt included with every conversation in the generated dataset.

system_prompt_updated_at
string<date-time> | null

Time system_prompt was last updated, in ISO 8601 format.

instructions
string | null

Natural-language description of the task the generated dataset should support.

instructions_updated_at
string<date-time> | null

Time instructions was last updated, in ISO 8601 format.

resolved_instructions
string | null
vector_database_id
string | null

ID of the vector database the data job draws on.

Last modified on November 4, 2026