---
title: "Create account balance history config v1"
method: POST
path: "/bank-statements/v1/account-balances/history/config"
tags: ["Bank statements"]
---

# Create account balance history config v1

`POST /bank-statements/v1/account-balances/history/config`

## Request

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

Create an account balance history configuration by division code.

The configuration becomes effective on the day after the cycle closing time plus the cycle event delay.
Example:
  - Division timezone: `UTC`
  - Create account balance history configuration is called at: `2023-05-01T18:00:00Z`
  - Account balance history configuration `cycle_closing_time` is: `22:00:00`
  - Account balance history configuration `cycle_event_delay` is: `10`
  - Account balance history configuration starts at `2023-05-01T22:10:00Z`

This endpoint generates an [Account balance history configuration created](https://developers.pismo.io/events/docs/account-balances-balance-history-config-creation-1) event.

## Request body

- CreateAccountBalanceHistoryConfigurationRequest: Create account balance history configuration request object
  - `division_code` string, required: Division code registered in the [Create division](https://developers.pismo.io/pismo-docs/reference/post-division-v2) endpoint.
  - `cycle_closing_time` string, time, required: Time of day the cycle closes for a division. This time follows the timezone configured in division. You can find the division timezone using the [Get division by code](https://developers.pismo.io/pismo-docs/reference/get-division-by-code-v2) endpoint.
  - `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.

## Response `201`

Created

- CreateAccountBalanceHistoryConfigurationResponse: Get account balance history configuration response object
  - `cycle_closing_time` string, time: Time of day the cycle closes for a division. This time follows the timezone configured in division. You can find the division timezone using the [Get division by code](https://developers.pismo.io/pismo-docs/reference/get-division-by-code-v2) endpoint.
  - `cycle_event_delay` integer: 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: 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)