Sign in

v27

latestOpenAPI 3.0.02026-07-1347144237.4 KB
UploadFile:

This completes the Upload, and the returned Upload object contains a nested File object that is ready for use across the platform. You can define the order of the Parts by providing an ordered list of Part IDs. The total number of bytes uploaded must match the size originally specified when creating the Upload object. After this operation no additional Parts can be added once the Upload is completed.

post/uploads/{upload-id}/complete

Path parameters

upload-idstring required

The identifier of the upload.

Query parameters

api-versionstring required

The requested API version.

Request body

part_idsstring[] required
md5string

Response

Success

object'list' | 'fine_tuning.job' | 'file' | 'fine_tuning.job.event' | 'fine_tuning.job.checkpoint' | 'model' | 'upload' | 'upload.part' | 'batch' | 'wandb'

Defines the type of an object.

created_atinteger

A timestamp when this job or item was created (in unix epochs).

idstring

The identity of this item.

bytesinteger
filenamestring
purpose'fine-tune' | 'fine-tune-results' | 'assistants' | 'assistants_output' | 'batch' | 'batch_output' | 'evals' | 'evals_output'

The intended purpose of the uploaded documents. Use "fine-tune" for fine-tuning. This allows us to validate the format of the uploaded file.

status'pending' | 'expired' | 'completed' | 'cancelled'
expires_atinteger