Get performance history

Returns historical Commander reporting data as rows: the same figures as the Reports page and its CSV download. With `group_by=time` (the default) it returns a timeseries, one row per `tick_size` bucket; other `group_by` values return one row per combination of the requested breakdowns. A missing value is `null`, never `0`. Requires a Commander Pro subscription (403 otherwise). **Measures and compatible `group_by` values** | Measure | Unit | Allowed `group_by` | | --- | --- | --- | | `hashrate` | H/s (Sol/s for `equihash`) | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id`, `miner_id` | | `power_consumption` | W | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id`, `miner_id` | | `efficiency` | J/TH | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id`, `miner_id` | | `temperature` | °C | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id`, `miner_id` | | `energy_consumption` | kWh | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id`, `miner_id` | | `site_load` | 0–1 ratio | `time`, `site` | | `online_miners` | mean concurrent count | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id` | | `hashing_miners` | mean concurrent count | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id` | | `failing_miners` | mean concurrent count | `time`, `site`, `model`, `firmware`, `subaccount`, `client_id` | | `new_miners` | count | `time`, `site`, `model`, `firmware`, `client_id` | | `new_errors` | count | `time`, `site`, `model`, `firmware`, `client_id` | | `unresolved_errors` | count | `time`, `site`, `model`, `firmware`, `client_id` | | `bulk_actions` | count | `time`, `site` | | `triggers_executed` | count | `time`, `site` | | `iminer_optimizations` | count | `time`, `site` | | `tickets_opened` | count | `time`, `site` | | `tickets_closed` | count | `time`, `site` | **Rules** - `miner_id` can only be combined with `time` and/or `site`, and requires a period of 31 days or less. - `efficiency` is `sha256` only. - `tick_size` is required when `group_by` includes `time`. - At most 5000 time buckets per request: `1h` covers about 208 days, `1d` covers about 13.7 years. - `start_date` must be before today (UTC), and `end_date` is clamped to the start of today: reports only cover complete days. - At most 100,000 rows in total. Narrow the period, the breakdowns or `site_ids` if you hit this. A request that breaks any rule, or names an unknown parameter or value, is rejected with 400 listing the violations found. A malformed or missing parameter is reported first, before the rules that combine parameters are checked. **Examples** Daily fleet timeseries: `GET /v2/commander/reports?start_date=2026-09-01&end_date=2026-09-28&measures=hashrate,power_consumption,hashing_miners&group_by=time&tick_size=1d` Energy by site by month: `GET /v2/commander/reports?start_date=2026-01-01&end_date=2026-06-30&measures=energy_consumption&group_by=time,site&tick_size=1M` Per-miner hashrate over a week: `GET /v2/commander/reports?site_ids=618ee7c5-bf5d-45b8-b845-b423cf5123d0&start_date=2026-09-21&end_date=2026-09-27&measures=hashrate,temperature&group_by=miner_id` Action counts by site: `GET /v2/commander/reports?start_date=2026-09-01&end_date=2026-09-28&measures=bulk_actions,triggers_executed,iminer_optimizations&group_by=site`