Baserow Representative API Octri Preview
POST/api/database/rows/table/{table_id}/batch/

Create rows in a database table in a batch

Creates multiple rows in a database table in one request. Include the field values for each new row in the items array, using field IDs as keys or enabling user_field_names to use field names. Row-created webhooks are not supported by this operation.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

8 parameters · 1 body field
table_idintegerrequired
The unique identifier of the table in which to create the rows.
beforeintegeroptional
The ID of an existing row to position the new rows before.
include_metadatabooleanoptional
When enabled, includes operation metadata describing changed field IDs and cascade updates.
send_webhook_eventsbooleanoptional
Whether to trigger webhooks after the operation. Accepts `y`, `yes`, `true`, `t`, `on`, `1`, or an empty value to enable; defaults to `true` when omitted.
user_field_namesbooleanoptional
When enabled with a truthy value such as `y`, `yes`, `true`, `t`, `on`, `1`, or an empty value, uses user-defined field names instead of internal names such as `field_123`.
viewintegeroptional
The ID of the view in which to create the rows; providing it can affect permission checks and default values.
ClientSessionIdstringoptional
An optional UUID identifying the client session, which can be used with undo or redo operations to reverse or repeat this action.
ClientUndoRedoActionGroupIdstringoptional
An optional UUID grouping this action with other actions for undo or redo.

Batch creation payload containing 1 to 200 row objects. Each row can include values for any supported table fields; omitted fields receive their default values.

itemsarray<object>required
Array of row objects to create. Must contain between 1 and 200 items.

4 status codes
200Returns an `items` array containing the created row objects.
itemsarray<object>required
400Returned when `items` is missing, contains fewer than 1 or more than 200 entries, or a field value fails validation.
detailstringoptional
Human readable details about what went wrong.
errorstringoptional
Machine readable error indicating what went wrong.
Allowed:ERROR_USER_NOT_IN_GROUPERROR_REQUEST_BODY_VALIDATIONERROR_ROW_IDS_NOT_UNIQUEERROR_REQUEST_BODY_VALIDATIONERROR_RICH_TEXT_IMAGE_LIMIT_EXCEEDEDERROR_USER_FILE_DOES_NOT_EXIST
401Returned when the authenticated user does not have permission to access the table.
detailstringoptional
Human readable details about what went wrong.
errorstringoptional
Machine readable error indicating what went wrong.
Allowed:ERROR_NO_PERMISSION_TO_TABLE
404Returned when the table or specified view does not exist.
detailstringoptional
Human readable details about what went wrong.
errorstringoptional
Machine readable error indicating what went wrong.
Allowed:ERROR_TABLE_DOES_NOT_EXISTERROR_ROW_DOES_NOT_EXISTERROR_VIEW_DOES_NOT_EXIST

Error handling

A 400 is returned when items is missing, contains fewer than 1 or more than 200 entries, or a field value fails validation. A 401 is returned when the authenticated user does not have permission to access the table. A 404 is returned when the table or specified view does not exist. The table_id path parameter must identify the table in which to create rows.