table-rows

Count the rows a filter selects

How many rows a predicate matches, with no rows read.

Takes the where and row_status vocabulary of the rows query, so a saved view's own filter can be counted by sending it back verbatim: that is how a picker can say what choosing a view will actually select before anything is bound to it.

An unfiltered count is free: it reads the table's maintained counter rather than scanning. A filtered one is an exact COUNT over the same predicate the listing applies, never an estimate, so the number cannot disagree with the rows the client goes on to fetch.

A POST for the same reason the rows query is one: a filter list has no honest query-string encoding.

post/tables/{table_id}/rows/count/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/tables/{table_id}/rows/count/
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

table_idstring uuid required

Request body

row_status'errored' | 'fully_computed'

A row-level state, derived from its cells rather than stored.

ERRORED is "any cell of this row failed to compute"; FULLY_COMPUTED is its exact complement, so the two partition the table. Serves the built-in smart views, which are questions about computation rather than about values. The ordinary filter vocabulary cannot express either.

Response

Successful Response

countinteger required

Rows matching the predicate. Exact, not an estimate.

Changes

No recorded changes to this operation across all 1 revision of this API.