Updates an existing row in the table if the user has access to the related table's workspace. The accepted body fields are depending on the fields that the table has. For a complete overview of fields use the list_database_table_fields endpoint to list them all. None of the fields are required, if they are not provided the value is not going to be updated. When you want to update a value for the field with id 10, the key must be named field_10. Or if the GET parameter user_field_names is provided the key of the field to update must be the name of the field. Multiple different fields to update can be provided in one request. In the examples below you will find all the different field types, the numbers/ids in the example are just there for example purposes, the field_ID must be replaced with the actual id of the field or the name of the field if user_field_names is provided.
Request
- Base URLhttps://api.baserow.io (the document declares no server; this is the origin it was published from)
- URLhttps://api.baserow.io/api/database/rows/table/{table_id}/{row_id}/
- Auth
- HTTP bearer
- or HTTP bearer
Path parameters
Updates the row related to the value.
Updates the row in the table related to the value.
Query parameters
A flag query parameter that triggers webhooks after the operation, if set to y, yes, true, t, on, 1, or left empty. Defaults to true
A flag query parameter that, if provided with one of the following values: y, yes, true, t, on, 1, or an empty value, will cause this endpoint to expect and return the user-specified field names instead of the internal Baserow field names (e.g., field_123).
Provide if the row is updated in a view. This can result in different permission checking and default values.
Headers
An optional header that marks the action performed by this request as having occurred in a particular client session. Then using the undo/redo endpoints with the same ClientSessionId header this action can be undone/redone.
An optional header that marks the action performed by this request as having occurred in a particular action group.Then calling the undo/redo endpoint with the same ClientSessionId header, all the actions belonging to the same action group can be undone/redone together in a single API call.
Request body
Response
Changes
- warning
added the new
ERROR_RICH_TEXT_IMAGE_LIMIT_EXCEEDEDenum value to theresponse property for the response status - warning
added the new
ERROR_USER_FILE_DOES_NOT_EXISTenum value to theresponse property for the response status - info
the endpoint scheme security
UserSource JWTwas removed from the API
- warning
- breaking
the
response property's maxLength was unset from1000000for the response status - warning
removed the request property
(media type: application/json) - warning
removed the request property
(media type: application/x-www-form-urlencoded) - warning
removed the request property
(media type: multipart/form-data) - info
added the new optional request property
(media type: application/json) - info
added the new optional request property
(media type: application/x-www-form-urlencoded) - info
added the new optional request property
(media type: multipart/form-data) - info
added the optional property
to the response with the status
- breaking