Every stock count on file, with its totals and the variance it found
One page of counts, newest scope first, each row carrying what the count covers and what it found: line_count and counted_line_count, the system_total and counted_total over the counted lines only, and variance_total (which is exactly counted_total - system_total) with variance_value_total beside it.
variance_value_total PRICES AN UNPRICED LINE AT ZERO. A counted line on a variant with no cost on file contributes nothing to the money while contributing its units to variance_total, so the two totals can disagree about how much of a count is accounted for. get_stocktake_lines_table serves unit_cost per line, and a null there is what the money is missing.
status is open or posted. An open count is still being counted and its figures move; a posted one is frozen and carries posted_at. Filter on it with filter_args=[{"key":"status","operation":"eq","value":"open"}], the only filterable key.
search matches the count's name. sort_args takes name, status, counted_on, line_count, variance_total or variance_value_total, prefixed - for descending. limit defaults to 10 and offset to 0; max_size is every count on file and filtered_max_size is how many the search and filters left, so a caller pages on the second.
id is a string on the wire and is what the by-id operations take. location_names is for display only. A count is scoped by location id at creation and the names are resolved on read.
Scope: stocktakes:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/stocktakes/table
- Auth: HTTP bearer
Query parameters
Match against the count's name. Omitted, every count is in scope.
How many rows to return. Defaults to 10; the platform cap is 10,000.
How many rows to skip. Page against filtered_max_size, not max_size.
Sort fields, comma-separated, - for descending and + or nothing for ascending. One of name, status, counted_on, line_count, variance_total, variance_value_total.
A JSON array of {key, operation, value}. status is the only key, taking eq, ne, in or nin against open and posted; in and nin take an array as the value.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
One page of counts, with the totals each one found.
Changes
No recorded changes to this operation across all 1 revision of this API.