---
title: "List account balance history config v2"
method: GET
path: "/bank-statements/v2/account-balances/history/config"
tags: ["Bank statements"]
---

# List account balance history config v2

`GET /bank-statements/v2/account-balances/history/config`

## Request

- Base URL: `https://sandbox.pismolabs.io/passport`
- URL: `https://sandbox.pismolabs.io/passport/bank-statements/v2/account-balances/history/config`
- Auth: none declared

List account balance history configurations by division, organization, or program ID.

## Query parameters

- `targetType` 'DIVISION' | 'ORGANIZATION' | 'PROGRAM', required
- `balanceHistoryConfigOffset` integer
- `balanceHistoryConfigLimit` integer

## Response `200`

Created

- ListAccountBalanceHistoryConfigurationResponsev2: Get account balance history configuration response object
  - `pagination` OffsetPagination: Data related to list pagination using an offset parameter
    - `has_next` boolean: Whether there are more pages after the current page (`true`) or not (`false`).
    - `limit` integer: Maximum number of items per page
    - `offset` integer: Starting index of the result list. Default is 0.
  - `items` object
    - `id` string, uuid, required: Balance history configuration ID
    - `target_type` 'ORGANIZATION' | 'PROGRAM' | 'DIVISION', required: Account balance history config target type
    - `target_id` string, required: Target ID. When `target_type` is `DIVISION`, this value is the division code. Likewise, when `target_type` is `PROGRAM`, the value is the program ID, and so on.
    - `cycle_closing_time` string, time, required: Cycle closing time indicates what time of day the cycle closes for a division, organization, or program. This time uses the timezone configured for the corresponding division, organization, or program.
    - `cycle_event_delay` integer, required: The cycle event delay specifies how many minutes after `cycle_closing_time` the account balance history event is issued for each account in the division.
    - `cycle_config_validity` CycleConfigValidity, required: The start and end date/time indicating when the cycle configuration becomes valid or invalid.
      - `start` string, datetime: The date and time when the configuration becomes valid. Format = `yyyy-mm-dd:hr:mm:ss`.
      - `end` string, datetime: The date and time when the configuration ends. Format = `yyyy-mm-dd:hr:mm:ss`.

## Other responses

- `400`: Bad Request
- `404`: Not Found
- `409`: Conflict
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/platform-authentication.md) - [All operations](https://skmtc.dev/pismo/apis/platform-authentication/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/platform-authentication/revisions/935b62e16de4?raw)