You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -353,6 +353,17 @@ Available only when [indexing](#indexing) is enabled.
353
353
| `GET` | `/index/query/runs` | Query indexed runs with PostgREST-style filtering, sorting, and pagination |
354
354
| `GET` | `/index/query/test_stats` | Query test stat data with PostgREST-style filtering, sorting, and pagination |
355
355
| `GET` | `/index/query/test_stats_block_logs` | Query per-block log data with PostgREST-style filtering, sorting, and pagination |
356
+
| `GET` | `/index/query/suites` | Query suite data with PostgREST-style filtering, sorting, and pagination |
357
+
358
+
#### Row count
359
+
360
+
By default, query endpoints skip the `SELECT count(*)` for performance — the `total` field is omitted from the response. To request an exact row count, send the `Prefer: count=exact` header:
361
+
362
+
```
363
+
Prefer: count=exact
364
+
```
365
+
366
+
When present, the response includes `"total": <n>`. This follows the [PostgREST](https://docs.postgrest.org/en/stable/references/api/preferences.html#exact-count) convention. On large tables (e.g. `test_stats`) the count query can take several seconds, so only request it when needed (e.g. for pagination totals).
356
367
357
368
### Files (requires authentication unless `anonymous_read` is enabled)
0 commit comments