GET /api/database/rows/table/{table_id}/{row_id}/

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.

Servers

Path parameters

Name Type Required Description
table_id Integer Yes

Returns the row of the table related to the provided value.

row_id Integer Yes

Returns the row related the provided value.

Query parameters

Name Type Required Description
user_field_names Boolean No

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).

include String No

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.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.