Add info about using CSV and TSV request bodies

Author: chkn

api-reference/v2/stashing/put-stashes-serial.mdx

@@ -5,6 +5,8 @@ openapi: put /stashes/{stashID}/{serial}
 
 When using large datasets with the Glide API, it may be necessary to break them into smaller chunks for performance and reliability. We call this process "stashing."
 
+Tabular data may be stashed in JSON, CSV, or TSV format.
+
 <Tip>
   To learn more about stashing and how to use it to work with large datasets, please see our [introduction to stashing](/api-reference/v2/stashing/introduction).
 </Tip>

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

@@ -5,6 +5,8 @@ openapi: post /tables/{tableID}/rows
 
 Add row data to an existing Big Table.
 
+Row data may be passed in JSON, CSV, or TSV format.
+
 ## Examples
 
 <AccordionGroup>

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

@@ -5,6 +5,8 @@ openapi: post /tables
 
 Create a new Big Table, define its structure, and (optionally) populate it with data.
 
+When using a CSV or TSV request body, the name of the table must be passed as a query parameter and the schema of the table is inferred from the content. Alternatively, the CSV/TSV content may be [stashed](/api-reference/v2/stashing/introduction), and then the schema and name may be passed in the regular JSON payload.
+
 ## Examples
 
 <AccordionGroup>

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

@@ -5,6 +5,8 @@ openapi: put /tables/{tableID}
 
 Overwrite an existing Big Table by clearing all rows and adding new data. You can also update the table schema.
 
+When using a CSV or TSV request body, you cannot pass a schema. The current schema will be used. If you need to update the schema, use the `onSchemaError=updateSchema` query parameter, or [stash](/api-reference/v2/stashing/introduction) the CSV/TSV data and pass a JSON request body.
+
 <Warning>
 This is a destructive operation that cannot be undone.
 </Warning>