.

Author: Will Hang

openapi.yaml

@@ -1729,7 +1729,7 @@ paths:
             tags:
                 - Uploads
             summary: |
-                Creates an intermediate [Upload](/docs/api-reference/uploads/object) object that you can add [Parts](/docs/api-reference/uploads/part-object) to. Currently, an Upload can accept at most 10 GB in total and expires after an hour after you create it.
+                Creates an intermediate [Upload](/docs/api-reference/uploads/object) object that you can add [Parts](/docs/api-reference/uploads/part-object) 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](/docs/api-reference/files/object) object that contains all the parts you uploaded. This File is usable in the rest of our platform as a regular File object.
 
@@ -1785,9 +1785,18 @@ paths:
             summary: |
                 Adds 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. 
 
-                Each Part can be at most 64 MB, and you can add Parts until you hit the Upload maximum of 10 GB.
+                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](/docs/api-reference/uploads/complete).
+            parameters:
+                - in: path
+                  name: upload_id
+                  required: true
+                  schema:
+                      type: string
+                      example: upload_abc123
+                  description: |
+                      The ID of the Upload.
             requestBody:
                 required: true
                 content:
@@ -1829,6 +1838,15 @@ paths:
                 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.
+            parameters:
+                - in: path
+                  name: upload_id
+                  required: true
+                  schema:
+                      type: string
+                      example: upload_abc123
+                  description: |
+                      The ID of the Upload.
             requestBody:
                 required: true
                 content:
@@ -1880,6 +1898,15 @@ paths:
                 - Uploads
             summary: |
                 Cancels the Upload. No Parts may be added after an Upload is cancelled.
+            parameters:
+                - in: path
+                  name: upload_id
+                  required: true
+                  schema:
+                      type: string
+                      example: upload_abc123
+                  description: |
+                      The ID of the Upload.
             responses:
                 "200":
                     description: OK
@@ -3865,7 +3892,7 @@ paths:
                 name: Retrieve message
                 group: threads
                 beta: true
-                returns: The [message](/docs/api-reference/threads/messages/object) object matching the specified ID.
+                returns: The [message](/docs/api-reference/messages/object) object matching the specified ID.
                 examples:
                     request:
                         curl: |
@@ -3953,7 +3980,7 @@ paths:
                 name: Modify message
                 group: threads
                 beta: true
-                returns: The modified [message](/docs/api-reference/threads/messages/object) object.
+                returns: The modified [message](/docs/api-reference/messages/object) object.
                 examples:
                     request:
                         curl: |
@@ -7642,7 +7669,7 @@ components:
                           description: The text contents of the message.
                           title: Text content
                         - type: array
-                          description: An array of content parts with a defined type, each can be of type `text` or `image_url` when passing in images. You can pass multiple images by adding multiple `image_url` content parts. Image input is only supported when using the `gpt-4-visual-preview` model.
+                          description: An array of content parts with a defined type, each can be of type `text` or `image_url` when passing in images. You can pass multiple images by adding multiple `image_url` content parts. Image input is only supported when using the `gpt-4o` model.
                           title: Array of content parts
                           items:
                               $ref: "#/components/schemas/ChatCompletionRequestMessageContentPart"