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.Servers
- https://api.openai.com/v1
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
upload_id |
String | Yes |
The ID of the Upload. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
md5 |
String | No |
The optional md5 checksum for the file contents to verify if the bytes uploaded matches what you expect. |
part_ids[] |
Array | Yes |
The ordered list of Part IDs. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.