Usage Reports and Activity

Pool consumption is captured in hourly and daily activity records, surfaced in the platform and available in full through the Management API.

Pool totals are aggregated once per day. The current day may not yet appear in a report, the charts indicate this below the toolbar when it applies.

Pool Usage Report

Every pool detail page ends with a Usage report section. The chart covers a selectable date range using the standard analytics date picker. Ranges of seven days or fewer switch automatically from daily to hourly resolution.

Two views are available:

Pool total: Shows the pool's cumulative consumption over time, split into consumed and overage bands. The maximum and overage limits are drawn as reference lines, and reset days are marked with green indicators.

By member: Shows a stacked area chart with one band per member. The busiest members appear individually; the remainder are grouped into Other members. A dashed line represents the pool total, and a legend shows each member's consumed units and its share of the pool.

View consumption events opens a raw event list alongside the chart every add, reset, and offline sync with its timestamp, member, and amount. Use the action filter to narrow the list. Negative additions are labeled Remove consumption.

Account Usage Report

The Consumption pools tab on a customer account includes an account-wide Usage report below the pools list. This chart shows one stacked band per pool (the busiest pools individually, the remainder as Other pools), a dashed All pools total line, and a legend with per-pool totals and shares. Reset markers identify which pool reset and when. The same date picker and daily/hourly resolution rule applies.

Exporting Data

Both the pool chart and the events drawer offer CSV export. Exporting requires the reporting data export feature on your plan.

Export source	Contents
Pool chart, Pool total view	The pool's hourly activity rows
Pool chart, By member view	Raw per-member activity rows
Events drawer	Raw per-member activity rows
Account chart	Per-pool activity rows (timestamp, action, consumptions, pool ID, customer account ID)

Exports always contain the underlying activity rows at hourly resolution, not the chart's derived running totals.

Raw Activity via the Management API

The same data is available through four endpoint families. See Management API Reference for the full filter reference.

Endpoint	Contents
/api/v1/consumption-pools-hourly/	Hourly pool activity, list, aggregate, export
/api/v1/consumption-pools-daily/	Daily pool activity, list, aggregate
/api/v1/license-consumption-activities/	Per-license consumption activity, raw, hourly, daily, export
/api/v1/license-feature-consumption-activities/	Per-feature consumption activity same actions

The aggregate action groups filtered rows by any combination of consumption_pool, customer_account, company, and action, always bucketed by time. It returns consumption sums per bucket per group, the building block for cross-pool and cross-account reports.

On the per-license and per-feature activity endpoints, each row carries a consumption_pool field. Rows attributed to a pool have it populated; standalone rows have it null. To retrieve only standalone consumption, filter with consumption_pool__isnull=true. To retrieve only pool-attributed rows, use consumption_pool or consumption_pool__in. Without a filter, both are returned together.

Activity action values: consumption_add, consumption_reset, and the offline sync action recorded when checkouts settle.

Example: Daily Consumption Per Pool for One Account

GET /api/v1/consumption-pools-daily/aggregate/?customer_account=42&group_by=consumption_pool,action&date__gte=2026-09-01&date__lte=2026-09-30

{
  "count": 3,
  "results": [
    { "date": "2026-09-08", "consumption_pool_id": 2, "action": "consumption_add", "consumptions": 720 },
    { "date": "2026-09-08", "consumption_pool_id": 1, "action": "consumption_reset", "consumptions": null },
    { "date": "2026-09-09", "consumption_pool_id": 2, "action": "consumption_add", "consumptions": 650 }
  ]
}

Analytics endpoints remain accessible even if the Consumption Pools feature is later removed from your plan. You retain API access to all historical data generated while the feature was active. Pool objects themselves are gated by the feature flag.