---
title: "List Table Records"
method: GET
path: "/api/v3/data/{baseId}/{tableId}/records"
tags: ["Table Records"]
---

# List Table Records

`GET /api/v3/data/{baseId}/{tableId}/records`

## Request

- Base URL: `https://app.nocodb.com`
- URL: `https://app.nocodb.com/api/v3/data/{baseId}/{tableId}/records`
- Auth: one of:
  - API key in header `xc-token`
  - HTTP bearer
- TypeScript: <https://skmtc.dev/nocodb/apis/nocodb-v3/docs/api/v3/data/:baseId/:tableId/records/get.ts> (a function with typed inputs; its response is checked against the schema)

This API endpoint allows you to retrieve records from a specified table. You can customize the response by applying various query parameters for filtering, sorting, and formatting.

**Pagination**: The response is paginated by default, with the first page being returned initially. The response includes the following pagination fields as top-level properties alongside `records`:

- **next**: URL to retrieve the next page of records. For example, `"https://app.nocodb.com/api/v3/tables/medhonywr18cysz/records?page=2"`. Returns `null` when on the last page.
- **prev**: URL to retrieve the previous page of records. Returns `null` when on the first page.
- **nestedNext**: URL to retrieve the current page of records with the next set of nested (linked record) data. Returns `null` when there are no more nested pages.
- **nestedPrev**: URL to retrieve the current page of records with the previous set of nested data. Returns `null` when on the first nested page.

These pagination fields are particularly valuable when working with large datasets divided into multiple pages. They provide the necessary URLs to seamlessly navigate forward and backward through the dataset.

## Query parameters

- `fields` union
  - string[]
  - string
- `sort` union
  - object[]
    - `direction` 'asc' | 'desc'
    - `field` string, required
  - object
    - `direction` 'asc' | 'desc'
    - `field` string, required
- `where` string
- `page` integer
- `nestedPage` integer
- `pageSize` integer
- `limit` integer
- `offset` integer
- `nestedLimit` integer
- `viewId` string
- `linksAsLtar` 'true'
- `fieldIdOnResult` 'true'

## Headers

- `xc-token` string, required

## Response `200`

OK

- DataListResponseV3: V3 Data List Response format
  - `records` DataRecordV3[]: Array of records for has-many and many-to-many relationships
    - `id` union, required: Record identifier (primary key value)
      - string
      - number
    - `id_fields` object: Individual primary key field values as object
    - `fields` object: Record fields data, excluding the primary key. Always present; an empty object when the record has no other fields.
    - `field_errors` string[]: Fields whose value could not be computed because the field is broken (e.g. a lookup through a deleted link). Their value in `fields` is null.
  - `next` string, nullable: Pagination token for next page
  - `prev` string, nullable: Pagination token for previous page
  - `nestedNext` string, nullable: Nested pagination token for next page
  - `nestedPrev` string, nullable: Nested pagination token for previous page

## Other responses

- `400`: BadRequest
- `422`: Unprocessable Entity — an unknown field in `fields` or `sort` (`ERR_FIELD_NOT_FOUND`), or a `page` below 1 (`ERR_INVALID_OFFSET_VALUE`).

## Changes

- **2026-10-13** `2ba4267a99d7`: 6 info
  - added the new optional `query` request parameter `fieldIdOnResult`
  - added the new optional `query` request parameter `limit`
  - added the new optional `query` request parameter `nestedLimit`
  - added the new optional `query` request parameter `offset`
  - …2 more

[Operation history](https://skmtc.dev/nocodb/apis/nocodb-v3/changes/api/v3/data/:baseId/:tableId/records/get.md)

---

[API](https://skmtc.dev/nocodb/apis/nocodb-v3.md) - [All operations](https://skmtc.dev/nocodb/apis/nocodb-v3/llms.txt) - [OpenAPI document](https://skmtc.dev/nocodb/apis/nocodb-v3/revisions/62a735aaf849?raw)