Reports

Renders a metric series to CSV asynchronously and returns a presigned download link when it is ready.

WHY ASYNCHRONOUS. A dashboard query is bounded — a chart nobody can render is worse than no chart — but an export has nobody watching, produces a file, and is usually wanted over a range no interactive query should attempt. Forcing both through one path means either the dashboard can hang or the export cannot cover a year.

AN IDENTICAL REQUEST IS REUSED. Asking twice for the same metric, grain, currency, range and dimension returns the export already pending or ready rather than rendering it again. A failed or expired one is not reused, so asking again after a failure means what you intend.

TWO IDENTICAL EXPORTS PRODUCE IDENTICAL BYTES, and therefore an identical sha256. Rows are sorted, buckets are rendered in UTC, values come from exact decimals rather than floats, and no run timestamp appears in the file — so the digest means 'the same data', not 'the same moment'.

Polls one export. download_url appears only once the status is ready, and expires with the export rather than later — a presigned link outliving the record it came from is tenant financial data reachable after the system stopped tracking that it was.

An id belonging to another organization answers 404 rather than 403: one that resolves for one tenant and forbids for another is an existence oracle.