Fetches an existing row from the table if the user has access to the related table's workspace. The properties of the returned row depend on which fields the table has. For a complete overview of fields use the list_database_table_fields endpoint to list them all. In the example all field types are listed, but normally the number in field_{id} key is going to be the id of the field of the field. Or if the GET parameter user_field_names is provided then the keys will be the name of the field. The value is what the user has provided and the format of it depends on the fields type.
Path parameters
Returns the row related the provided value.
Returns the row of the table related to the provided value.
Query parameters
Optionally include row's metadata in the response. The metadata object includes extra row specific data like the 'row_comments_notification_mode' settings, if available.
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 the returned JSON to use the user-specified field names instead of the internal Baserow field names (e.g., field_123).
Provide if the row if fetched in a view. This can result in different permission checking and default values.
Response
Changes
Changed in 1 of the 6 revisions of this API.11
- ▲
the
field_28response property's maxLength was unset from1000000for the response status200response-property-max-length-unset
- ○
added the optional property
field_29to the response with the200statusresponse-optional-property-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲