Skip to main content
PUT
File Upload

Purpose values and file formats

Each purpose value requires a specific JSONL schema. Each line of the file must be a valid JSON object matching the format for the chosen purpose.

fine-tune and alignment

Each line requires a messages array of {"role", "content"} objects. Valid roles are system, user, and assistant.

preference-fine-tune

Each line requires three fields — messages, chosen, and rejected — each an array of {"role", "content"} objects.

pre-train

Each line requires a single text field containing raw training text.

Authorizations

Authorization
string
header
required

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

Body

multipart/form-data
purpose
enum<string>
required

File purposes accepted by user-facing upload endpoints.

Available options:
reinforcement-fine-tune,
fine-tune,
preference-fine-tune,
pre-train,
alignment
files
file
required

File to upload.

vector_database_id
string | null

Response

Success

Files API response type

id
string
required

ID of the file.

object
string
required
Allowed value: "file"
created_at
string<date-time> | null

Time the file was created, in ISO 8601 format.

type

Type of the file.

Available options:
jsonl,
parquet,
pt
purpose
enum<string> | null

Purpose the file was uploaded for.

Available options:
reinforcement-fine-tune,
fine-tune,
preference-fine-tune,
pre-train,
alignment
filename
string | null

Name of the file.

bytes
integer | null

Size of the file in bytes.

created_by
string | null

Whether a user or the system created the file.

original_file_id
string | null

ID of the file this file was created from.

deleted
boolean | null

If true, the file was deleted.

Last modified on October 28, 2026