---
title: "Create operation block"
method: POST
path: "/corporate/v2/operations-blocks"
tags: ["Operations blocks"]
---

# Create operation block

`POST /corporate/v2/operations-blocks`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/corporate/v2/operations-blocks`
- Auth: HTTP bearer

**NOTE**: This v2 endpoint serves as a replacement for the v1 version.

Creates an operation block for a division or program. This block prevents transactions from being executed within the specified division or program, unless certain operations are explicitly allowed to bypass the restriction.

If neither `division_code` nor `program_id` is provided, the operation block is created for the whole organization.

## Request body

- CreateOperationsBlockV2Request: Create operations block request body
  - `description` string, required: Operations block description
  - `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.
  - `program_id` integer: Program ID. The program must belong to the organization. Use [List programs](https://developers.pismo.io/pismo-docs/reference/programs-1) to view a list of the program IDs for the organization. This program must be bound to the division. You can attach the program with either of the following endpoints: [Create division](ref:post-division-v2) [Patch division](ref:patch-division-v2)
  - `allowed_operations` OperationsBlocksOperation[]: List of operations allowed to bypass the block enforcement logic.<br> - `EARMARK_RELEASE`: Release an earmark even when an operation block is active. - `EARMARK_UPDATE`: Update an earmark (set amount, increase, or decrease) while the account is blocked by an operation block. - `PAYMENT_DEBIT`: Execute a debit transaction while the account is blocked by an operation block. - `PAYMENT_CREDIT`: Execute a credit transaction while the account is blocked by an operation block. - `PAYMENT_CONFIRM`: Confirm a value transaction while the account is blocked by an operation block. - `PAYMENT_CANCEL`: Cancel an existing transaction while the account is blocked by an operation block. - `ACCOUNT_STATUS_UPDATE`: Change the account status and the associated status reason. - `CHECK_POST`: Post a check while the account is blocked by an operation block. - `CHECK_RELEASE`: Release an uncleared check or operation while the account is blocked by an operation block. - `CHECK_CANCEL`: Cancel an existing check while the account is blocked by an operation block. - `RESTRICTED_FUNDS_CREATE`: Hold a specified amount by transferring it from the available balance to restricted funds. - `RESTRICTED_FUNDS_RELEASE`: Release restricted funds from hold. This transfers funds from restricted funds back to available balance.

## Response `201`

Created

- OperationsBlockV2: Operations block
  - `block_id` string, uuid, required: Operations block ID
  - `description` string, required: Operations block description
  - `status` 'ACTIVE' | 'DEACTIVATED', required: Status of the operations block.
  - `created_at` string, date-time, required: Operation block creation timestamp (ISO 8601). Format = `YYYY-MM-DDTHH:mm:ss.sssssssssZ`.
  - `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.
  - `program_id` integer: Program ID. The program must belong to the organization. Use [List programs](https://developers.pismo.io/pismo-docs/reference/programs-1) to view a list of the program IDs for the organization. This program must be bound to the division. You can attach the program with either of the following endpoints: [Create division](ref:post-division-v2) [Patch division](ref:patch-division-v2)
  - `allowed_operations` OperationsBlocksOperation[]: List of operations allowed to bypass the block enforcement logic.<br> - `EARMARK_RELEASE`: Release an earmark even when an operation block is active. - `EARMARK_UPDATE`: Update an earmark (set amount, increase, or decrease) while the account is blocked by an operation block. - `PAYMENT_DEBIT`: Execute a debit transaction while the account is blocked by an operation block. - `PAYMENT_CREDIT`: Execute a credit transaction while the account is blocked by an operation block. - `PAYMENT_CONFIRM`: Confirm a value transaction while the account is blocked by an operation block. - `PAYMENT_CANCEL`: Cancel an existing transaction while the account is blocked by an operation block. - `ACCOUNT_STATUS_UPDATE`: Change the account status and the associated status reason. - `CHECK_POST`: Post a check while the account is blocked by an operation block. - `CHECK_RELEASE`: Release an uncleared check or operation while the account is blocked by an operation block. - `CHECK_CANCEL`: Cancel an existing check while the account is blocked by an operation block. - `RESTRICTED_FUNDS_CREATE`: Hold a specified amount by transferring it from the available balance to restricted funds. - `RESTRICTED_FUNDS_RELEASE`: Release restricted funds from hold. This transfers funds from restricted funds back to available balance.
  - `updated_at` string, date-time: Operation block last update timestamp (ISO 8601). Format = `YYYY-MM-DDTHH:mm:ss.sssssssssZ`.

## Other responses

- `400`: Bad Request
- `401`: Access token is missing or invalid
- `403`: The request has been lost
- `409`: Conflict
- `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)