---
title: "Reserve Latency"
method: GET
path: "/btc/exchange-flows/reserve/latency"
tags: ["Latency"]
---

# Reserve Latency

`GET /btc/exchange-flows/reserve/latency`

Reports how fresh this metric's data is. **Append `/latency` to ANY v1 data endpoint** (e.g. `/btc/network-data/hashrate/latency`) to get the same shape for that metric.

- `block` — seconds from a block until the data point is **collectable**.
- `process` — seconds from a block until the data point is **fully processed and queryable**.
- `mutable` — whether already-served values may still be revised.

Values are reported per resolution (`block` / `hour` / `day` / `min`) and averaging window. See the [Data Latency guide](/guides/data-latency) for how to read them.

## Response `200`

Latency broken down by resolution and averaging window.

- object
  - `status` object
    - `code` integer
    - `message` string
  - `result` object
    - `data` object[]
      - `all_parameters` boolean
      - `block` object[]
      - `hour` object[]
      - `day` object[]

---

[API](https://skmtc.net/cryptoquant/apis/cryptoquant-data-api.md) · [All operations](https://skmtc.net/cryptoquant/apis/cryptoquant-data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cryptoquant/cryptoquant-data-api/revisions/81ee223d4908/schema)