Counts the rows of `table` — the same residual-free access path `SELECT COUNT(*) FROM table` would use via `/sql`, without a SQL round trip. A view answers 404 here, same as `GET …/rows` (no row-level resource in v1).

GET

/store-api/rel/{domain}/tables/{table}/count

curl --request GET \
  --url https://example.com/store-api/rel/example/tables/example/count \
  --header 'Authorization: Bearer <token>'

Authorizations

• bearer_auth

Parameters

Path Parameters

domain

required

string

Relational domain

table

required

string

Table name

Responses

200

Row count. A full key scan under the hood — cost grows linearly with table size; meant for on-demand use, not high-frequency polling.

Media typeapplication/json

Generic {"count": N} response, shared by JSON’s count_documents, KV’s count_keys, and rel’s count_rows — one schema instead of three identical ones.

object

count

required

integer format: int64

Example ^generated

{
  "count": 1
}

404

Domain or table not found (a view has no count resource, same as rows)

Media typetext/plain

string

410

Domain is being deleted

Media typetext/plain

string

429

Per-domain request budget exceeded

Media typetext/plain

string

503

Relational engine disabled

Media typetext/plain

string