# How to Get CS2 Item Supply and Sale Volume

> `POST /v1/archive/history` returns `total_supply` and `hourly_volume` together
> on the `aggregate` source from 2023. The same bucket also carries price and
> active-market fields for context.

Supply and sale volume measure different things. `total_supply` is an
approximate level observed at a point in time, while `hourly_volume` is an
approximate activity metric accumulated for the interval.

## Data available in one archive series

The aggregate archive can include:

- `total_supply`, approximate cumulative item supply.
- `hourly_volume`, approximate sale activity.
- Last-observed `ask`, `bid`, `ask_volume`, and `bid_volume`.
- `time`, the actual last observation inside the aligned `bucket`.
- `sample_count`, the observations represented by that bucket.

Coverage begins in 2023. Requests support `1h` and `1d`, and the archive
updates once or twice per day. At the daily interval, `hourly_volume` represents
the volume aggregated across the hours in that day.

## Analyze the fields on a shared timeline

Request the exact `market_hash_name`, choose the `aggregate` source, and use
`1h` for hourly archive buckets or `1d` for long-range daily analysis.

Compare the first and last observed `total_supply` values to describe supply
change. Sum daily `hourly_volume` values once to obtain approximate period
volume; multiplying a daily value by 24 would count the aggregation twice.

Keep each field's usable date span explicit. The first bucket containing supply
can differ from the first bucket containing an ask or volume value. Use the
outer `bucket` for alignment and `time` for the actual last observation.

The [archive endpoint reference](/docs/api-reference/archive-history) lists the
aggregate object. Use [CS2 sale volume data](/resources/how-to-get-cs2-sale-volume)
when the choice between aggregate, CSFloat, and Steam volume changes the
analysis.

## Applicable endpoint

| Endpoint | Returns | Plans |
| --- | --- | --- |
| `POST /v1/archive/history` | Price, approximate `total_supply`, and `hourly_volume` from 2023 | Scale, Enterprise |

## Keep the measurements separate

- Subtracting period volume from supply change does not produce net issuance
  or unique sales. The series have different definitions.
- `ask_volume` is active listing count and `bid_volume` is active buy-order
  count. Neither can replace `hourly_volume`.
- A sudden negative supply move can reflect changed coverage. Check adjacent
  observations before interpreting it as an in-game supply event.
- Use the CSFloat or Steam sale archives when the volume must be tied to one
  marketplace's completed-sale or purchase history.