> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/statistics/fetch-cumulative-volume.md).

# GET /stats/volume

Cumulative traded volume.

`operationId`: `fetchCumulativeVolume`

**Authentication:** none — this operation is public.

Cumulative traded notional in quote (USDX): the sum of `price * quantity` over deduplicated `Fill` events, counted once per fill (a fill carries both sides of the trade, so it is not doubled), liquidation prints included. Delisted markets keep contributing — a cumulative total must not fall when a market leaves the listing.

Returned as decimal STRINGS, not JSON numbers. The same accumulator reaches `GET /markets/summary` and `GET /tickers` through a lossy `f64` conversion; this route does not, so the two surfaces can disagree in the last digits and this one is the exact figure.

**This is not a 24h window.** `MarketSummary.volume_24h` and `Ticker.quoteVolume` are the SAME accumulator under a misleading name: nothing decays either of them. Read `GET /stats/volume` when you want the cumulative figure stated honestly, with the coverage start that says what it is cumulative since.

**`coverage_start_ms` is part of the contract, not a nicety.** The figure is NOT cumulative since inception. This is an in-memory projection: whenever it is rebuilt, the total restarts from zero and `coverage_start_ms` moves forward with it. So compare the two across scrapes — a `coverage_start_ms` later than the one you saw last is what distinguishes a reset from a quiet venue, and a consumer that publishes the total alone is publishing a number that can silently drop. `testnet` is always `true` and `note` restates this in prose.

## Responses

| Status | Body                                                                    | Meaning                                                |
| ------ | ----------------------------------------------------------------------- | ------------------------------------------------------ |
| `200`  | [`CumulativeVolume`](/api-reference/guides/schemas.md#cumulativevolume) | Cumulative traded notional, venue total and per market |

## Example

```bash
curl -X GET 'https://exchange.nexus.xyz/api/exchange/stats/volume'
```

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.27`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexus.xyz/api-reference/statistics/fetch-cumulative-volume.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.