Uploads

Create upload

post /uploads

Creates an intermediate Upload object that you can add Parts to. Currently, an Upload can accept at most 8 GB in total and expires after an hour after you create it.

Once you complete the Upload, we will create a File object that contains all the parts you uploaded. This File is usable in the rest of our platform as a regular File object.

For certain purpose values, the correct mime_type must be specified. Please refer to documentation for the supported MIME types for your use case.

For guidance on the proper filename extensions for each purpose, please follow the documentation on creating a File.

Returns the Upload object with status pending.

Body Parameters

bytes: number

The number of bytes in the file you are uploading.
filename: string

The name of the file to upload.
mime_type: string

The MIME type of the file.

This must fall within the supported MIME types for your file purpose. See the supported MIME types for assistants and vision.
purpose: "assistants" or "batch" or "fine-tune" or "vision"

The intended purpose of the uploaded file.

See the documentation on File purposes.
- "assistants"
- "batch"
- "fine-tune"
- "vision"
expires_after: optional object { anchor, seconds }

The expiration policy for a file. By default, files with purpose=batch expire after 30 days and all other files are persisted until they are manually deleted.
- anchor: "created_at"
  
  Anchor timestamp after which the expiration policy applies. Supported anchors: created_at.
  - "created_at"
- seconds: number
  
  The number of seconds after the anchor time that the file will expire. Must be between 3600 (1 hour) and 2592000 (30 days).

Returns

Upload object { id, bytes, created_at, 6 more }

The Upload object can accept byte chunks in the form of Parts.
- id: string
  
  The Upload unique identifier, which can be referenced in API endpoints.
- bytes: number
  
  The intended number of bytes to be uploaded.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Upload was created.
- expires_at: number
  
  The Unix timestamp (in seconds) for when the Upload will expire.
- filename: string
  
  The name of the file to be uploaded.
- purpose: string
  
  The intended purpose of the file. Please refer here for acceptable values.
- status: "pending" or "completed" or "cancelled" or "expired"
  
  The status of the Upload.
  - "pending"
  - "completed"
  - "cancelled"
  - "expired"
- file: optional FileObject
  
  The File object represents a document that has been uploaded to OpenAI.
  - id: string
    
    The file identifier, which can be referenced in the API endpoints.
  - bytes: number
    
    The size of the file, in bytes.
  - created_at: number
    
    The Unix timestamp (in seconds) for when the file was created.
  - filename: string
    
    The name of the file.
  - object: "file"
    
    The object type, which is always file.
    - "file"
  - purpose: "assistants" or "assistants_output" or "batch" or 5 more
    
    The intended purpose of the file. Supported values are assistants, assistants_output, batch, batch_output, fine-tune, fine-tune-results, vision, and user_data.
    - "assistants"
    - "assistants_output"
    - "batch"
    - "batch_output"
    - "fine-tune"
    - "fine-tune-results"
    - "vision"
    - "user_data"
  - status: "uploaded" or "processed" or "error"
    
    Deprecated. The current status of the file, which can be either uploaded, processed, or error.
    - "uploaded"
    - "processed"
    - "error"
  - expires_at: optional number
    
    The Unix timestamp (in seconds) for when the file will expire.
  - status_details: optional string
    
    Deprecated. For details on why a fine-tuning training file failed validation, see the error field on fine_tuning.job.
- object: optional "upload"
  
  The object type, which is always "upload".
  - "upload"

Example

curl https://api.openai.com/v1/uploads \
    -H 'Content-Type: application/json' \
    -H "Authorization: Bearer $OPENAI_API_KEY" \
    -d '{
          "bytes": 0,
          "filename": "filename",
          "mime_type": "mime_type",
          "purpose": "assistants"
        }'

Response

{
  "id": "id",
  "bytes": 0,
  "created_at": 0,
  "expires_at": 0,
  "filename": "filename",
  "purpose": "purpose",
  "status": "pending",
  "file": {
    "id": "id",
    "bytes": 0,
    "created_at": 0,
    "filename": "filename",
    "object": "file",
    "purpose": "assistants",
    "status": "uploaded",
    "expires_at": 0,
    "status_details": "status_details"
  },
  "object": "upload"
}

Example

curl https://api.openai.com/v1/uploads \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
    "purpose": "fine-tune",
    "filename": "training_examples.jsonl",
    "bytes": 2147483648,
    "mime_type": "text/jsonl",
    "expires_after": {
      "anchor": "created_at",
      "seconds": 3600
    }
  }'

Response

{
  "id": "upload_abc123",
  "object": "upload",
  "bytes": 2147483648,
  "created_at": 1719184911,
  "filename": "training_examples.jsonl",
  "purpose": "fine-tune",
  "status": "pending",
  "expires_at": 1719127296
}

Complete upload

post /uploads/{upload_id}/complete

Completes the Upload.

Within the returned Upload object, there is a nested File object that is ready to use in the rest of the platform.

You can specify the order of the Parts by passing in an ordered list of the Part IDs.

The number of bytes uploaded upon completion must match the number of bytes initially specified when creating the Upload object. No Parts may be added after an Upload is completed. Returns the Upload object with status completed, including an additional file property containing the created usable File object.

Path Parameters

upload_id: string

Body Parameters

part_ids: array of string

The ordered list of Part IDs.
md5: optional string

The optional md5 checksum for the file contents to verify if the bytes uploaded matches what you expect.

Returns

Upload object { id, bytes, created_at, 6 more }

The Upload object can accept byte chunks in the form of Parts.
- id: string
  
  The Upload unique identifier, which can be referenced in API endpoints.
- bytes: number
  
  The intended number of bytes to be uploaded.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Upload was created.
- expires_at: number
  
  The Unix timestamp (in seconds) for when the Upload will expire.
- filename: string
  
  The name of the file to be uploaded.
- purpose: string
  
  The intended purpose of the file. Please refer here for acceptable values.
- status: "pending" or "completed" or "cancelled" or "expired"
  
  The status of the Upload.
  - "pending"
  - "completed"
  - "cancelled"
  - "expired"
- file: optional FileObject
  
  The File object represents a document that has been uploaded to OpenAI.
  - id: string
    
    The file identifier, which can be referenced in the API endpoints.
  - bytes: number
    
    The size of the file, in bytes.
  - created_at: number
    
    The Unix timestamp (in seconds) for when the file was created.
  - filename: string
    
    The name of the file.
  - object: "file"
    
    The object type, which is always file.
    - "file"
  - purpose: "assistants" or "assistants_output" or "batch" or 5 more
    
    The intended purpose of the file. Supported values are assistants, assistants_output, batch, batch_output, fine-tune, fine-tune-results, vision, and user_data.
    - "assistants"
    - "assistants_output"
    - "batch"
    - "batch_output"
    - "fine-tune"
    - "fine-tune-results"
    - "vision"
    - "user_data"
  - status: "uploaded" or "processed" or "error"
    
    Deprecated. The current status of the file, which can be either uploaded, processed, or error.
    - "uploaded"
    - "processed"
    - "error"
  - expires_at: optional number
    
    The Unix timestamp (in seconds) for when the file will expire.
  - status_details: optional string
    
    Deprecated. For details on why a fine-tuning training file failed validation, see the error field on fine_tuning.job.
- object: optional "upload"
  
  The object type, which is always "upload".
  - "upload"

Example

curl https://api.openai.com/v1/uploads/$UPLOAD_ID/complete \
    -H 'Content-Type: application/json' \
    -H "Authorization: Bearer $OPENAI_API_KEY" \
    -d '{
          "part_ids": [
            "string"
          ]
        }'

Response

{
  "id": "id",
  "bytes": 0,
  "created_at": 0,
  "expires_at": 0,
  "filename": "filename",
  "purpose": "purpose",
  "status": "pending",
  "file": {
    "id": "id",
    "bytes": 0,
    "created_at": 0,
    "filename": "filename",
    "object": "file",
    "purpose": "assistants",
    "status": "uploaded",
    "expires_at": 0,
    "status_details": "status_details"
  },
  "object": "upload"
}

Example

curl https://api.openai.com/v1/uploads/upload_abc123/complete
  -d '{
    "part_ids": ["part_def456", "part_ghi789"]
  }'

Response

{
  "id": "upload_abc123",
  "object": "upload",
  "bytes": 2147483648,
  "created_at": 1719184911,
  "filename": "training_examples.jsonl",
  "purpose": "fine-tune",
  "status": "completed",
  "expires_at": 1719127296,
  "file": {
    "id": "file-xyz321",
    "object": "file",
    "bytes": 2147483648,
    "created_at": 1719186911,
    "expires_at": 1719127296,
    "filename": "training_examples.jsonl",
    "purpose": "fine-tune",
  }
}

Cancel upload

post /uploads/{upload_id}/cancel

Cancels the Upload. No Parts may be added after an Upload is cancelled.

Returns the Upload object with status cancelled.

Path Parameters

upload_id: string

Returns

Upload object { id, bytes, created_at, 6 more }

The Upload object can accept byte chunks in the form of Parts.
- id: string
  
  The Upload unique identifier, which can be referenced in API endpoints.
- bytes: number
  
  The intended number of bytes to be uploaded.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Upload was created.
- expires_at: number
  
  The Unix timestamp (in seconds) for when the Upload will expire.
- filename: string
  
  The name of the file to be uploaded.
- purpose: string
  
  The intended purpose of the file. Please refer here for acceptable values.
- status: "pending" or "completed" or "cancelled" or "expired"
  
  The status of the Upload.
  - "pending"
  - "completed"
  - "cancelled"
  - "expired"
- file: optional FileObject
  
  The File object represents a document that has been uploaded to OpenAI.
  - id: string
    
    The file identifier, which can be referenced in the API endpoints.
  - bytes: number
    
    The size of the file, in bytes.
  - created_at: number
    
    The Unix timestamp (in seconds) for when the file was created.
  - filename: string
    
    The name of the file.
  - object: "file"
    
    The object type, which is always file.
    - "file"
  - purpose: "assistants" or "assistants_output" or "batch" or 5 more
    
    The intended purpose of the file. Supported values are assistants, assistants_output, batch, batch_output, fine-tune, fine-tune-results, vision, and user_data.
    - "assistants"
    - "assistants_output"
    - "batch"
    - "batch_output"
    - "fine-tune"
    - "fine-tune-results"
    - "vision"
    - "user_data"
  - status: "uploaded" or "processed" or "error"
    
    Deprecated. The current status of the file, which can be either uploaded, processed, or error.
    - "uploaded"
    - "processed"
    - "error"
  - expires_at: optional number
    
    The Unix timestamp (in seconds) for when the file will expire.
  - status_details: optional string
    
    Deprecated. For details on why a fine-tuning training file failed validation, see the error field on fine_tuning.job.
- object: optional "upload"
  
  The object type, which is always "upload".
  - "upload"

Example

curl https://api.openai.com/v1/uploads/$UPLOAD_ID/cancel \
    -X POST \
    -H "Authorization: Bearer $OPENAI_API_KEY"

Response

{
  "id": "id",
  "bytes": 0,
  "created_at": 0,
  "expires_at": 0,
  "filename": "filename",
  "purpose": "purpose",
  "status": "pending",
  "file": {
    "id": "id",
    "bytes": 0,
    "created_at": 0,
    "filename": "filename",
    "object": "file",
    "purpose": "assistants",
    "status": "uploaded",
    "expires_at": 0,
    "status_details": "status_details"
  },
  "object": "upload"
}

Example

curl https://api.openai.com/v1/uploads/upload_abc123/cancel

Response

{
  "id": "upload_abc123",
  "object": "upload",
  "bytes": 2147483648,
  "created_at": 1719184911,
  "filename": "training_examples.jsonl",
  "purpose": "fine-tune",
  "status": "cancelled",
  "expires_at": 1719127296
}

Domain Types

Upload

Upload object { id, bytes, created_at, 6 more }

The Upload object can accept byte chunks in the form of Parts.
- id: string
  
  The Upload unique identifier, which can be referenced in API endpoints.
- bytes: number
  
  The intended number of bytes to be uploaded.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Upload was created.
- expires_at: number
  
  The Unix timestamp (in seconds) for when the Upload will expire.
- filename: string
  
  The name of the file to be uploaded.
- purpose: string
  
  The intended purpose of the file. Please refer here for acceptable values.
- status: "pending" or "completed" or "cancelled" or "expired"
  
  The status of the Upload.
  - "pending"
  - "completed"
  - "cancelled"
  - "expired"
- file: optional FileObject
  
  The File object represents a document that has been uploaded to OpenAI.
  - id: string
    
    The file identifier, which can be referenced in the API endpoints.
  - bytes: number
    
    The size of the file, in bytes.
  - created_at: number
    
    The Unix timestamp (in seconds) for when the file was created.
  - filename: string
    
    The name of the file.
  - object: "file"
    
    The object type, which is always file.
    - "file"
  - purpose: "assistants" or "assistants_output" or "batch" or 5 more
    
    The intended purpose of the file. Supported values are assistants, assistants_output, batch, batch_output, fine-tune, fine-tune-results, vision, and user_data.
    - "assistants"
    - "assistants_output"
    - "batch"
    - "batch_output"
    - "fine-tune"
    - "fine-tune-results"
    - "vision"
    - "user_data"
  - status: "uploaded" or "processed" or "error"
    
    Deprecated. The current status of the file, which can be either uploaded, processed, or error.
    - "uploaded"
    - "processed"
    - "error"
  - expires_at: optional number
    
    The Unix timestamp (in seconds) for when the file will expire.
  - status_details: optional string
    
    Deprecated. For details on why a fine-tuning training file failed validation, see the error field on fine_tuning.job.
- object: optional "upload"
  
  The object type, which is always "upload".
  - "upload"

Parts

Add upload part

post /uploads/{upload_id}/parts

Adds a Part to an Upload object. A Part represents a chunk of bytes from the file you are trying to upload.

Each Part can be at most 64 MB, and you can add Parts until you hit the Upload maximum of 8 GB.

It is possible to add multiple Parts in parallel. You can decide the intended order of the Parts when you complete the Upload.

Path Parameters

upload_id: string

Returns

UploadPart object { id, created_at, object, upload_id }

The upload Part represents a chunk of bytes we can add to an Upload object.
- id: string
  
  The upload Part unique identifier, which can be referenced in API endpoints.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Part was created.
- object: "upload.part"
  
  The object type, which is always upload.part.
  - "upload.part"
- upload_id: string
  
  The ID of the Upload object that this Part was added to.

Example

curl https://api.openai.com/v1/uploads/$UPLOAD_ID/parts \
    -H 'Content-Type: multipart/form-data' \
    -H "Authorization: Bearer $OPENAI_API_KEY" \
    -F 'data=@/path/to/data'

Response

{
  "id": "id",
  "created_at": 0,
  "object": "upload.part",
  "upload_id": "upload_id"
}

Example

curl https://api.openai.com/v1/uploads/upload_abc123/parts
  -F data="aHR0cHM6Ly9hcGkub3BlbmFpLmNvbS92MS91cGxvYWRz..."

Response

{
  "id": "part_def456",
  "object": "upload.part",
  "created_at": 1719185911,
  "upload_id": "upload_abc123"
}

Domain Types

Upload Part

UploadPart object { id, created_at, object, upload_id }

The upload Part represents a chunk of bytes we can add to an Upload object.
- id: string
  
  The upload Part unique identifier, which can be referenced in API endpoints.
- created_at: number
  
  The Unix timestamp (in seconds) for when the Part was created.
- object: "upload.part"
  
  The object type, which is always upload.part.
  - "upload.part"
- upload_id: string
  
  The ID of the Upload object that this Part was added to.

resources/uploads/index.md +71 −44

4 4

5**post** `/uploads`5**post** `/uploads`

6 6

~~7Create upload~~7Creates an intermediate [Upload](/docs/api-reference/uploads/object) object

8that you can add [Parts](/docs/api-reference/uploads/part-object) to.

9Currently, an Upload can accept at most 8 GB in total and expires after an

10hour after you create it.

12Once you complete the Upload, we will create a

13[File](/docs/api-reference/files/object) object that contains all the parts

14you uploaded. This File is usable in the rest of our platform as a regular

15File object.

17For certain `purpose` values, the correct `mime_type` must be specified.

18Please refer to documentation for the

19[supported MIME types for your use case](/docs/assistants/tools/file-search#supported-files).

21For guidance on the proper filename extensions for each purpose, please

22follow the documentation on [creating a

23File](/docs/api-reference/files/create).

25Returns the Upload object with status `pending`.

8 26

9### Body Parameters27### Body Parameters

10 28

23 This must fall within the supported MIME types for your file purpose. See41 This must fall within the supported MIME types for your file purpose. See

24 the supported MIME types for assistants and vision.42 the supported MIME types for assistants and vision.

25 43

~~26- `purpose: FilePurpose`~~44- `purpose: "assistants" or "batch" or "fine-tune" or "vision"`

27 45

28 The intended purpose of the uploaded file.46 The intended purpose of the uploaded file.

29 47

30 See the [documentation on File48 See the [documentation on File

~~31 purposes](https://platform.openai.com/docs/api-reference/files/create#files-create-purpose).~~49 purposes](/docs/api-reference/files/create#files-create-purpose).

32 50

33 - `"assistants"`51 - `"assistants"`

34 52

38 56

39 - `"vision"`57 - `"vision"`

40 58

~~41 - `"user_data"`~~

~~43 - `"evals"`~~

45- `expires_after: optional object { anchor, seconds }`59- `expires_after: optional object { anchor, seconds }`

46 60

47 The expiration policy for a file. By default, files with `purpose=batch` expire after 30 days and all other files are persisted until they are manually deleted.61 The expiration policy for a file. By default, files with `purpose=batch` expire after 30 days and all other files are persisted until they are manually deleted.

82 96

83 The name of the file to be uploaded.97 The name of the file to be uploaded.

84 98

~~85 - `object: "upload"`~~

~~87 The object type, which is always "upload".~~

~~89 - `"upload"`~~

91 - `purpose: string`99 - `purpose: string`

92 100

~~93 The intended purpose of the file. [Please refer here](https://platform.openai.com/docs/api-reference/files/object#files/object-purpose) for acceptable values.~~101 The intended purpose of the file. [Please refer here](/docs/api-reference/files/object#files/object-purpose) for acceptable values.

94 102

95 - `status: "pending" or "completed" or "cancelled" or "expired"`103 - `status: "pending" or "completed" or "cancelled" or "expired"`

96 104

168 176

169 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.177 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.

170 178

179 - `object: optional "upload"`

180

181 The object type, which is always "upload".

182

183 - `"upload"`

184

171### Example185### Example

172 186

173```http187```http

191 "created_at": 0,205 "created_at": 0,

192 "expires_at": 0,206 "expires_at": 0,

193 "filename": "filename",207 "filename": "filename",

194 "object": "upload",

195 "purpose": "purpose",208 "purpose": "purpose",

196 "status": "pending",209 "status": "pending",

197 "file": {210 "file": {

204 "status": "uploaded",217 "status": "uploaded",

205 "expires_at": 0,218 "expires_at": 0,

206 "status_details": "status_details"219 "status_details": "status_details"

207 }220 },

221 "object": "upload"

208}222}

209```223```

210 224

244 258

245**post** `/uploads/{upload_id}/complete`259**post** `/uploads/{upload_id}/complete`

246 260

247Complete upload261Completes the [Upload](/docs/api-reference/uploads/object).

262

263Within the returned Upload object, there is a nested [File](/docs/api-reference/files/object) object that is ready to use in the rest of the platform.

264

265You can specify the order of the Parts by passing in an ordered list of the Part IDs.

266

267The number of bytes uploaded upon completion must match the number of bytes initially specified when creating the Upload object. No Parts may be added after an Upload is completed.

268Returns the Upload object with status `completed`, including an additional `file` property containing the created usable File object.

248 269

249### Path Parameters270### Path Parameters

250 271

286 307

287 The name of the file to be uploaded.308 The name of the file to be uploaded.

288 309

289 - `object: "upload"`

~~290~~

291 The object type, which is always "upload".

~~292~~

293 - `"upload"`

~~294~~

295 - `purpose: string`310 - `purpose: string`

296 311

297 The intended purpose of the file. [Please refer here](https://platform.openai.com/docs/api-reference/files/object#files/object-purpose) for acceptable values.312 The intended purpose of the file. [Please refer here](/docs/api-reference/files/object#files/object-purpose) for acceptable values.

298 313

299 - `status: "pending" or "completed" or "cancelled" or "expired"`314 - `status: "pending" or "completed" or "cancelled" or "expired"`

300 315

372 387

373 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.388 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.

374 389

390 - `object: optional "upload"`

391

392 The object type, which is always "upload".

393

394 - `"upload"`

395

375### Example396### Example

376 397

377```http398```http

394 "created_at": 0,415 "created_at": 0,

395 "expires_at": 0,416 "expires_at": 0,

396 "filename": "filename",417 "filename": "filename",

397 "object": "upload",

398 "purpose": "purpose",418 "purpose": "purpose",

399 "status": "pending",419 "status": "pending",

400 "file": {420 "file": {

407 "status": "uploaded",427 "status": "uploaded",

408 "expires_at": 0,428 "expires_at": 0,

409 "status_details": "status_details"429 "status_details": "status_details"

410 }430 },

431 "object": "upload"

411}432}

412```433```

413 434

448 469

449**post** `/uploads/{upload_id}/cancel`470**post** `/uploads/{upload_id}/cancel`

450 471

451Cancel upload472Cancels the Upload. No Parts may be added after an Upload is cancelled.

473

474Returns the Upload object with status `cancelled`.

452 475

453### Path Parameters476### Path Parameters

454 477

480 503

481 The name of the file to be uploaded.504 The name of the file to be uploaded.

482 505

483 - `object: "upload"`

~~484~~

485 The object type, which is always "upload".

~~486~~

487 - `"upload"`

~~488~~

489 - `purpose: string`506 - `purpose: string`

490 507

491 The intended purpose of the file. [Please refer here](https://platform.openai.com/docs/api-reference/files/object#files/object-purpose) for acceptable values.508 The intended purpose of the file. [Please refer here](/docs/api-reference/files/object#files/object-purpose) for acceptable values.

492 509

493 - `status: "pending" or "completed" or "cancelled" or "expired"`510 - `status: "pending" or "completed" or "cancelled" or "expired"`

494 511

566 583

567 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.584 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.

568 585

586 - `object: optional "upload"`

587

588 The object type, which is always "upload".

589

590 - `"upload"`

591

569### Example592### Example

570 593

571```http594```http

583 "created_at": 0,606 "created_at": 0,

584 "expires_at": 0,607 "expires_at": 0,

585 "filename": "filename",608 "filename": "filename",

586 "object": "upload",

587 "purpose": "purpose",609 "purpose": "purpose",

588 "status": "pending",610 "status": "pending",

589 "file": {611 "file": {

596 "status": "uploaded",618 "status": "uploaded",

597 "expires_at": 0,619 "expires_at": 0,

598 "status_details": "status_details"620 "status_details": "status_details"

599 }621 },

622 "object": "upload"

600}623}

601```624```

602 625

649 672

650 The name of the file to be uploaded.673 The name of the file to be uploaded.

651 674

652 - `object: "upload"`

~~653~~

654 The object type, which is always "upload".

~~655~~

656 - `"upload"`

~~657~~

658 - `purpose: string`675 - `purpose: string`

659 676

660 The intended purpose of the file. [Please refer here](https://platform.openai.com/docs/api-reference/files/object#files/object-purpose) for acceptable values.677 The intended purpose of the file. [Please refer here](/docs/api-reference/files/object#files/object-purpose) for acceptable values.

661 678

662 - `status: "pending" or "completed" or "cancelled" or "expired"`679 - `status: "pending" or "completed" or "cancelled" or "expired"`

663 680

735 752

736 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.753 Deprecated. For details on why a fine-tuning training file failed validation, see the `error` field on `fine_tuning.job`.

737 754

755 - `object: optional "upload"`

756

757 The object type, which is always "upload".

758

759 - `"upload"`

760

738# Parts761# Parts

739 762

740## Add upload part763## Add upload part

741 764

742**post** `/uploads/{upload_id}/parts`765**post** `/uploads/{upload_id}/parts`

743 766

744Add upload part767Adds a [Part](/docs/api-reference/uploads/part-object) to an [Upload](/docs/api-reference/uploads/object) object. A Part represents a chunk of bytes from the file you are trying to upload.

768

769Each Part can be at most 64 MB, and you can add Parts until you hit the Upload maximum of 8 GB.

770

771It is possible to add multiple Parts in parallel. You can decide the intended order of the Parts when you [complete the Upload](/docs/api-reference/uploads/complete).

745 772

746### Path Parameters773### Path Parameters

747 774

resources/uploads/index.md 2026-07-10 23:02 UTC to 2026-07-12 06:58 UTC

Uploads

Create upload

Body Parameters

Returns

Example

Response

Example

Response

Complete upload

Path Parameters

Body Parameters

Returns

Example

Response

Example

Response

Cancel upload

Path Parameters

Returns

Example

Response

Example

Response

Domain Types

Upload

Parts

Add upload part

Path Parameters

Returns

Example

Response

Example

Response

Domain Types

Upload Part