Skip to main content
The inventory and changes endpoints expose Azure Resource Graph snapshot data enriched with cost, utilization, and opportunity signals — plus consecutive-snapshot diffs for drift detection. All endpoints require a reader or admin session and support pagination. Export variants stream up to 50,000 rows as CSV or XLSX.

GET /api/inventory

Returns a paginated, filterable view of the Azure estate. Each resource record is enriched with monthly cost estimates, utilization telemetry, and the highest-severity opportunity Flux has detected for that resource. Authentication: reader

Query parameters

Response

Each item in items contains:

Example


GET /api/inventory/export

Streams the full filtered inventory as a CSV or XLSX file. Accepts the same filter parameters as GET /api/inventory and can return up to 50,000 rows. Authentication: reader

Additional parameter

XLSX exports include a Metadata sheet recording the generation timestamp, analytics read mode, active snapshot version (when applicable), and all applied filters. This preserves provenance for downstream spreadsheet workflows. The CSV and XLSX column set matches the full items field list from GET /api/inventory, with tags and effectiveVirtualTags serialized as compact JSON strings.

GET /api/changes

Returns paginated inventory diffs between consecutive Azure Resource Graph snapshots, capturing resource additions, deletions, property changes, and cost movements. Authentication: reader

Query parameters

Response

Each change record includes the affected resource’s identity fields, the detected change type, the before/after property evidence, and the observation timestamps for both snapshots.

Example


GET /api/changes/anomalies

Returns the current change-volume baselines and any statistically anomalous change volumes detected across the estate. Flux uses a median/MAD (median absolute deviation) baseline computed over the configured observation history — the same statistical approach used for cost anomalies. This endpoint is also accessible at the legacy path GET /api/anomalies. Authentication: reader No query parameters. The response contains the estate-level and per-scope baselines, the current-window change counts, computed k-scores, and any scopes that exceed the anomaly threshold.

Example