List Saved Tables
Every table saved on your account, with its
tableID.Get Table Data
Re-run one table for a date range and get its rows.
Before you start
- Labby AI must be enabled on the labs the table reads. Labs without it are skipped; if none are left, the call returns
403. - Credentials are the same Client ID and Client Secret as every other Flabs API (Authentication). You can also find a table’s ID and your Client ID under Get API on the table in Labby AI. The secret comes from Flabs support.
How a call works
- Always the latest version. Each call re-runs the table’s current saved recipe. Edit the table in Labby AI (add a column, a formula, a filter) and the next API call returns the new shape. Read your columns from
data.columnson every call; don’t hard-code them. - Dates are IST.
gte=2026-11-01<e=2026-11-30means 1 Nov 00:00 IST to 30 Nov 23:59:59.999 IST. You can also pass full ISO 8601 timestamps. One call covers at most 30 days, both ends included (1–30 Nov is allowed, 1 Nov–1 Dec is not); for a longer period, call once per month and combine. - Labs. By default a table reads the labs it was saved with. Pass
labIDsto narrow a multi-lab table to some of them, or to switch a single-lab table to another of your labs. - Up to 5,000 rows per call. When a range holds more,
data.truncatedis set and only the first 5,000 rows come back. Split the range. - Formula columns you added in Labby AI are computed for you and come back like any other column. A formula that can’t be computed for a row is
null. - Tables built from an uploaded document (
refreshable: false) can’t be re-run for a date range; their data call returns409.
Rate limits
Each data call runs a fresh query over your lab data, so refresh on a schedule (for example every hour) rather than on every page view. If you refresh many tables at once, spread the calls out: the 20-per-minute limit is for the whole account.
Errors and retries
Errors use the standard Flabs error format; the reason is inerror.details.
Never retry
422 or 429 in a tight loop. A 422 usually means the query is heavy, and
re-sending it only adds load; a 429 keeps failing until the minute resets.