List time estimates
Returns one result per requested ID in request order, after checking card access. An available result with a null estimate authoritatively means there is no stored estimate; a stored cleared estimate has estimate_seconds=0 and retains its kind and version. Only an available positive estimate matches Has time estimate. Unavailable results disclose no estimate, distinguish neither missing from restricted cards nor their metadata, and must never be treated as No time estimate. A failed or incomplete backend batch returns an error, never fabricated absent rows. Reads do not traverse hierarchies and roadmap project estimates do not depend on one space’s time-logging switch.
Authorizations
Path Parameters
Query Parameters
Response
Authoritative per-ID estimate availability.
Examples of authoritative empty and unavailable results respectively:
{"card_id":"2702","status":"available","estimate":null} and
{"card_id":"2703","status":"unavailable","estimate":null}.
These must not be conflated. The structured example shows an estimated leaf
and a cleared budget retaining its kind and concurrency version.