Docs: Clarify order preservation for returned row IDs

api-reference/v2/general/limits.mdx

@@ -16,4 +16,6 @@ Even when using stashing, there are limits to the number of rows you can work wi
 |---------------------------------------------------------------|------------|
 | [Create Table](/api-reference/v2/tables/post-tables)          | 8m         |
 | [Overwrite Table](/api-reference/v2/tables/put-tables)        | 8m         |
-| [Add Rows to Table](/api-reference/v2/tables/post-table-rows) | 250k       |
+| [Add Rows to Table](/api-reference/v2/tables/post-table-rows) | 250k       |
+
+When adding rows to a table, the returned row IDs are guaranteed to be in the same order as the input rows provided in the request.

api-reference/v2/resources/changelog.mdx

@@ -3,6 +3,10 @@ title: Glide API Changelog
 sidebarTitle: Changelog
 ---
 
+### January 15, 2025
+
+- Clarified that for endpoints returning row IDs, the IDs are returned in the same order as the input rows.
+
 ### November 26, 2024
 
 - Added a warning that using the `PUT /tables` endpoint to overwrite a table will clear user-specific columns.
@@ -83,3 +87,5 @@ sidebarTitle: Changelog
 - Support for creating, overwriting tables
 - Support for adding rows to tables
 - Support for stashing large datasets
+</fileContent>
+</invoke>

api-reference/v2/stashing/introduction.mdx

@@ -44,7 +44,7 @@ The following endpoints support the use of a stash. Please see the specific endp
 
 * [Create Table](/api-reference/v2/tables/post-tables)
 * [Overwrite Table](/api-reference/v2/tables/put-tables)
-* [Add Rows to Table](/api-reference/v2/tables/post-table-rows)
+* [Add Rows to Table](/api-reference/v2/tables/post-table-rows) - When using this endpoint, the row IDs in the response are returned in the same order as the input rows in your request.
 
 ## Use Cases
 

api-reference/v2/tables/post-table-rows.mdx

@@ -42,3 +42,5 @@ Row data may be passed in JSON, CSV, or TSV format.
     ```
   </Accordion>
 </AccordionGroup>
+
+The returned row IDs will be in the same order as the input rows provided in the request.

api-reference/v2/tables/post-tables.mdx

@@ -27,6 +27,8 @@ When using a CSV or TSV request body, the name of the table must be passed as a
     }
     ```
 
+    The response will include row IDs for all created rows, returned in the same order as the input rows.
+
     However, this is only appropriate for relatively small initial datasets (around a few hundred rows or less, depending on schema complexity). If you need to work with a larger dataset you should utilize stashing.
   </Accordion>
   <Accordion title="Create Table from Stash">

api-reference/v2/tutorials/bulk-import.mdx

@@ -89,6 +89,8 @@ To create a table with the data of the stash ID `20240501-import` you can use th
 }
 ```
 
+The endpoint will return a list of row IDs in the same order as the rows in your stashed data, preserving the order defined by the serial numbers in your stash uploads.
+
 ### Add Rows to Table
 
 To add data to an existing table you can use the [add rows to table](/api-reference/v2/tables/post-table-rows) endpoint with the `stashID` reference of `20240501-import` instead of the actual row values.
@@ -99,6 +101,8 @@ To add data to an existing table you can use the [add rows to table](/api-refere
 }
 ```
 
+The endpoint will return a list of row IDs in the same order as the rows in your stashed data, preserving the order defined by the serial numbers in your stash uploads.
+
 ### Overwrite Table
 
 To reset an existing table's data you can use the [overwrite table](/api-reference/v2/tables/put-tables) endpoint with the `stashID` reference of `20240501-import` instead of the actual row values.