The ID of the fine-tuning job to cancel.
Example:ft-AF1WoRqd3aJAHsqc9NY7iL8F
The ID of the fine-tuning job to cancel.
Example:ft-AF1WoRqd3aJAHsqc9NY7iL8F
OK
The fine_tuning.job object represents a fine-tuning job that has been created through the API.
The object identifier, which can be referenced in the API endpoints.
The Unix timestamp (in seconds) for when the fine-tuning job was created.
For fine-tuning jobs that have failed, this will contain more information on the cause of the failure.
The name of the fine-tuned model that is being created. The value will be null if the fine-tuning job is still running.
The Unix timestamp (in seconds) for when the fine-tuning job was finished. The value will be null if the fine-tuning job is still running.
The hyperparameters used for the fine-tuning job. This value will only be returned when running supervised jobs.
The base model that is being fine-tuned.
The object type, which is always “fine_tuning.job”.
Allowed values:fine_tuning.job
The organization that owns the fine-tuning job.
The compiled results file ID(s) for the fine-tuning job. You can retrieve the results with the Files API.
Example:file-abc123
The current status of the fine-tuning job, which can be either validating_files, queued, running, succeeded, failed, or cancelled.
Allowed values:validating_filesqueuedrunningsucceededfailedcancelled
The total number of billable tokens processed by this fine-tuning job. The value will be null if the fine-tuning job is still running.
The file ID used for training. You can retrieve the training data with the Files API.
The file ID used for validation. You can retrieve the validation results with the Files API.
One OfA list of integrations to enable for this fine-tuning job.
<= 5 items
The seed used for the fine-tuning job.
The Unix timestamp (in seconds) for when the fine-tuning job is estimated to finish. The value will be null if the fine-tuning job is not running.
The method used for fine-tuning.
Identifier for the last checkpoint ID from the previous pagination request.
Number of checkpoints to retrieve.
Default:10
The ID of the fine-tuning job to get checkpoints for.
Example:ft-AF1WoRqd3aJAHsqc9NY7iL8F
OK
The fine_tuning.job.checkpoint object represents a model checkpoint for a fine-tuning job that is ready to use.
Allowed values:list
Identifier for the last event from the previous pagination request.
Number of events to retrieve.
Default:20
The ID of the fine-tuning job to get events for.
Example:ft-AF1WoRqd3aJAHsqc9NY7iL8F
OK
Fine-tuning job event object
Allowed values:list
Create large batches of API requests to run asynchronously.
The ID of an uploaded file that contains requests for the new batch.
See upload file for how to upload a file.
Your input file must be formatted as a JSONL file, and must be uploaded with the purpose batch. The file can contain up to 50,000 requests, and can be up to 200 MB in size.
The endpoint to be used for all requests in the batch. Currently /v1/chat/completions, /v1/embeddings, and /v1/completions are supported. Note that /v1/embeddings batches are also restricted to a maximum of 50,000 embedding inputs across all requests in the batch.
Allowed values:/v1/chat/completions/v1/embeddings/v1/completions
The time frame within which the batch should be processed. Currently only 24h is supported.
Allowed values:24h
Set of 16 key-value pairs that can be attached to an object. This can be
useful for storing additional information about the object in a structured
format, and querying for objects via API or the dashboard.
Keys are strings with a maximum length of 64 characters. Values are strings
with a maximum length of 512 characters.
Batch created successfully.
The object type, which is always batch.
Allowed values:batch
The OpenAI API endpoint used by the batch.
The ID of the input file for the batch.
The time frame within which the batch should be processed.
The current status of the batch.
Allowed values:validatingfailedin_progressfinalizingcompletedexpiredcancellingcancelled
The ID of the file containing the outputs of successfully executed requests.
The ID of the file containing the outputs of requests with errors.
The Unix timestamp (in seconds) for when the batch was created.
The Unix timestamp (in seconds) for when the batch started processing.
The Unix timestamp (in seconds) for when the batch will expire.
The Unix timestamp (in seconds) for when the batch started finalizing.
The Unix timestamp (in seconds) for when the batch was completed.
The Unix timestamp (in seconds) for when the batch failed.
The Unix timestamp (in seconds) for when the batch expired.
The Unix timestamp (in seconds) for when the batch started cancelling.
The Unix timestamp (in seconds) for when the batch was cancelled.
The request counts for different statuses within the batch.
Set of 16 key-value pairs that can be attached to an object. This can be
useful for storing additional information about the object in a structured
format, and querying for objects via API or the dashboard.
Keys are strings with a maximum length of 64 characters. Values are strings
with a maximum length of 512 characters.