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.

api-versionstring required

The requested API version.

part_idsstring[] required

md5string

Success

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

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

Changed in 3 of the 26 revisions of this API.23

Jul 13, 20262022-03-01-previewb177dc430e3912See the full diff
- ▲
  added required request body
  request-body-added-required
- ○
  added the media type application/json for the response with the status
  response-media-type-added
- ○
  added the media type application/json for the response with the status
  response-media-type-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 13, 20262022-03-01-previewdf4579cc5f4f1See the full diff
- ○
  endpoint added
  endpoint-added
Jul 22, 20222022-03-01-preview9d525b5caa311See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 149 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog