---
title: "Release check"
method: POST
path: "/corporate/v1/checks/release"
tags: ["Check posting"]
---

# Release check

`POST /corporate/v1/checks/release`

Releases a check using the provided payload.

**NOTES**:
- This endpoint requires an account token - an access token encoded with an external account ID. Tokens can expire quickly, which can result in a `401 Unauthorized` message.

This endpoint generates the following events:
  - [Platform authorization created](https://developers.pismo.io/events/docs/platform-authorization-platform-authorization-1)
  - [Check posting status change](https://developers.pismo.io/events/docs/cash-management-check-status-change-1)

See [Data and reporting](https://developers.pismo.io/pismo-docs/docs/data-reporting-overview) for more information about events and setting up event notifications.

## Request body

- CheckReleaseRequest — Request to release a check.
  - `check_id` string, required — Check ID.
  - `tracking_id` string — Tracking ID associated with the check release transaction.
  - `settlement_date` string, date — The settlement date defined in the settlement to be released. <b>Notes</b>: - The settlement date must follow the ISO 8601 format (`yyyy-mm-dd`). - If you don't specify a date, the full check amount is released. - If provided, it must match the settlement date of one of the check's settlements.

## Response `202`

Check release accepted

- CheckReleaseResponse — Response for check release.
  - `check_id` string, required — Check ID.

## Other responses

- `400` — Bad Request
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `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-service-production.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)