---
title: "Count rows in a table"
method: POST
path: "/v1/table/{id}/count_rows"
tags: ["Table", "Data"]
---

# Count rows in a table

`POST /v1/table/{id}/count_rows`

Count the number of rows in table `id`

REST NAMESPACE ONLY
REST namespace returns the response as a plain integer
instead of the `CountTableRowsResponse` JSON object.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- CountTableRowsRequest
  - `id` string[]
  - `version` integer — Version of the table to describe. If not specified, server should resolve it to the latest version.
  - `predicate` string — Optional SQL predicate to filter rows for counting

## Response `200`

Result of counting rows in a table

- integer — Response containing the count of rows. Serializes transparently as just the number for backward compatibility.

## Other responses

- `400` — Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware.
- `401` — Unauthorized. The request lacks valid authentication credentials for the operation.
- `403` — Forbidden. Authenticated user does not have the necessary permissions.
- `404` — A server-side problem that means can not find the specified resource.
- `503` — The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry.
- `5XX` — A server-side problem that might not be addressable from the client side. Used for server 5xx errors without more specific documentation in individual routes.

## Changes

- **2025-12-20** `5d6099d672d3` — 6 breaking, 6 warning, 6 info
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `400`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `401`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `403`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `404`
  - …14 more
- **2025-12-11** `6ad4337e3849` — 1 warning, 1 info
  - removed the request property `filter`
  - added the new optional request property `predicate`
- **2025-07-29** `40a3bc489d46` — 6 breaking, 12 warning, 12 info
  - the response property `type` became optional for the status `400`
  - the response property `type` became optional for the status `401`
  - the response property `type` became optional for the status `403`
  - the response property `type` became optional for the status `404`
  - …26 more
- **2025-07-25** `8769f8e36bc4` — 2 warning, 1 info
  - removed the request property `name`
  - removed the request property `namespace`
  - added the new optional request property `id`
- **2025-07-22** `ac7519693c52` — 4 info
  - api tag `Data` added
  - api tag `Metadata` removed
  - added the new optional request property `filter`
  - added the new optional request property `version`

[Full history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/table/:id/count_rows/post.md)

---

[API](https://skmtc.dev/lance-format/apis/lance-namespace-specification.md) · [All operations](https://skmtc.dev/lance-format/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/lance-format/lance-namespace-specification/revisions/5d6099d672d3/schema)