---
title: "Update division"
method: PATCH
path: "/corporate/v2/divisions/{divisionCode}"
tags: ["Divisions"]
---

# Update division

`PATCH /corporate/v2/divisions/{divisionCode}`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/corporate/v2/divisions/{divisionCode}`
- Auth: HTTP bearer

Updates a division. Only provided fields are updated. Other fields are left unchanged.

This endpoint generates a [Corporate division updated](https://developers.pismo.io/events/docs/corporate-division-change-2) event.

## Path parameters

- `divisionCode` string, required

## Request body

- PatchDivisionRequestV2: Patch division request body
  - `division_code` string: Code used to identify your division within the organization. Division code should only contain letters, numbers, and hyphens. This is a client-provided ID and can be changed.
  - `hierarchy_id` string, uuid: Hierarchy ID generated by the [Create hierarchy](https://developers.pismo.io/pismo-docs/reference/post-hierarchies) endpoint.
  - `level_id` string, uuid: Level ID generated by the [Create hierarchy](https://developers.pismo.io/pismo-docs/reference/post-hierarchies) endpoint.
  - `administrative_division_id` integer: Administrative division ID. Specifying an administrative division ID in this field links your division to it. This is useful when you want to use the holidays defined in that administrative division.<br> **NOTE**: `administrative_division_id` points to [holiday calendar](ref:post-add-holiday-to-calendar). Administrative division is deprecated and replaced by holiday calendar, and both continue to use the same underlying data structure for backward compatibility. The administrative division ID is functionally equivalent to `holiday_calendar_id` and refers to the calendar that defines holidays and working days. For more information, refer to [Add holiday](ref:post-add-holiday-to-calendar).
  - `name` string: Division name
  - `parent_code` string: Division code that can be set as the parent of the division being created. The parent must be at a level with a lower index than the division being created. It must comply with the rule `^[a-zA-Z0-9-]+$`.
  - `description` string, nullable: Division description
  - `timezone` string: Division timezone in timezone database format.<br> This value is used in the calculations for holidays, weekends, and daily balances. If a timezone is not specified, the division inherits the timezone from its parent division. If the parent division also lacks a specified timezone, Pismo defaults to using UTC. To clear this field, specify an empty string.
  - `program_ids` integer[]: List of allowed program IDs. The programs must belong to the organization. This list is used for validation during the [Create transaction banking account](ref:post-account) process. You can retrieve the organization programs using the [List programs](ref:programs-1) endpoint. If no program IDs are specified, this division inherits the `program_ids` list from the parent division, if it exists.
  - `schema` SchemaCreateTransactionBankingAccount: Valid JSON Schema as defined at https://json-schema.org/specification.html. This schema validates the JSON custom fields used in the [Create transaction banking account](ref:post-account) process. If this field is not set, the division inherits its schema from the parent division, if one exists. The example below is shown in YAML for readability; the API requires JSON.

## Response `204`

No Content

## Other responses

- `400`: Bad Request
- `401`: Access token is missing or invalid
- `403`: The request has been lost
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/banking-transaction-banking.md) - [All operations](https://skmtc.dev/pismo/apis/banking-transaction-banking/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/banking-transaction-banking/revisions/1334306c9303?raw)