---
title: "Statistics:Volume"
method: GET
path: "/v2/statistics/volume"
tags: ["Statistics"]
---

# Statistics:Volume

`GET /v2/statistics/volume`

Get volume statistical information regarding your transactions. You can use the results to build a graphical representation regarding the volumes processed.

## Response `200`

OK

- StatisticStatisticVolumeOutput — Represents volume statistics broken down by weekly and daily periods.
  - `weekly` StatisticStatisticVolumeOutputWeeklyOutput[], nullable — Collection of Statistic.StatisticVolumeWeeklyOutput objects or an empty array
    - `year` integer — The identifier for the year
    - `week` integer — The identifier for the week
    - `paymentMethods` StatisticStatisticVolumeOutputPaymentMethodOutput[], nullable — The array of payment methods
      - `id` integer — The identifier of the payment profile
      - `label` string — Payment profile name
      - `volume` integer — Payment profile volume (in cents)
      - `transactions` integer — Amount of transactions for this paymentProfile
      - `uniquePayers` integer — Amount of unique customerKeys
      - `direction` 'DEBIT' | 'CREDIT' — Direction either CREDIT or DEBIT
      - `collecting` boolean — Is PAY "in the money flow"
  - `daily` StatisticStatisticVolumeOutputDailyOutput[], nullable — Collection of Statistic.StatisticVolumeDailyOutput objects or an empty array
    - `year` integer — The identifier for the year
    - `day` integer — The identifier for the day
    - `paymentMethods` StatisticStatisticVolumeOutputPaymentMethodOutput[], nullable — The array of payment methods
      - `id` integer — The identifier of the payment profile
      - `label` string — Payment profile name
      - `volume` integer — Payment profile volume (in cents)
      - `transactions` integer — Amount of transactions for this paymentProfile
      - `uniquePayers` integer — Amount of unique customerKeys
      - `direction` 'DEBIT' | 'CREDIT' — Direction either CREDIT or DEBIT
      - `collecting` boolean — Is PAY "in the money flow"

## Other responses

- `400` — Bad request, see response body for more information
- `401` — Unauthorized. Supplied credentials are invalid
- `403` — Forbidden. Supplied credentials have no rights
- `404` — Resource not found
- `405` — Used HTTP method is not allowed
- `406` — Not acceptable. The supplied content type in the accept parameter in the header is not supported
- `410` — Indicates that this resource is no longer available for use
- `415` — Unsupported media. The supplied content type in the content-type parameter in the header is not supported
- `429` — Rate limit reached.
- `500` — An internal error occurred.
- `503` — The server is currently unable to handle your request

---

[API](https://skmtc.dev/pay/apis/pay-transaction-gateway-unit-api.md) · [All operations](https://skmtc.dev/pay/apis/pay-transaction-gateway-unit-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pay/pay-transaction-gateway-unit-api/revisions/2bc260c7bdfc/schema)