> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Midaz Cycle 6 API updates

> New Midaz Cycle 6 endpoints for Ledger Settings, Balance History, and bidirectional Transaction Routes, with updated error codes and OpenAPI alignment.

<Badge stroke icon="calendar-days" iconType="regular">March 30, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## Affects

***

Teams using affected Midaz APIs or planning Cycle 6 integration changes.

This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.

## What changed

***

The Midaz API documentation has been updated to reflect all changes shipped in **Cycle 6**. This includes new endpoints, updated schemas, additional query filters, and new error codes — all localized in English, Portuguese, and Spanish.

### New endpoints

***

### Ledger Settings

Two new endpoints allow you to manage per-Ledger validation rules via the API:

* [**Retrieve Ledger Settings**](/en/reference/midaz/retrieve-ledger-settings) — `GET /organizations/{id}/ledgers/{id}/settings`
* [**Update Ledger Settings**](/en/reference/midaz/update-ledger-settings) — `PATCH /organizations/{id}/ledgers/{id}/settings`

These endpoints control whether **Account Type validation** and **Route validation** are enforced for a specific Ledger.

### Balance History

Two new endpoints support **point-in-time balance queries** for auditing, reconciliation, and historical reporting:

* [**Retrieve Balance History**](/en/reference/midaz/retrieve-balance-history) — Get the state of a specific balance at a given timestamp.
* [**Retrieve Balance History by Account**](/en/reference/midaz/retrieve-balance-history-by-account) — Get the state of all balances for an account at a given timestamp.

<Warning>
  The `date` parameter is required and must follow the format `yyyy-mm-dd hh:mm:ss`. If no balance data exists for the specified timestamp, a `404` error is returned.
</Warning>

### Updated schemas

***

### Transaction Routing

* **Operation Routes** now include `accountingEntries` and support a `bidirectional` route type
* **Transaction Routes** use a new `operationRoutes` object format
* **Operations** include new fields: `direction`, `routeId`, and `routeCode`

The [Transaction Routing](/en/midaz/transaction-routing-entities) guide was updated to reflect the new structure and behavior.

### New query filters

***

| Endpoint           | New filters                       |
| ------------------ | --------------------------------- |
| List Organizations | `legal_name`, `doing_business_as` |
| List Ledgers       | `name`                            |
| List Operations    | `direction`, `route_id`           |

### New error codes

***

Error codes **0140–0158** were added to the [error reference](/en/reference/midaz/error-list), covering validation failures for the new Ledger Settings and routing features.

### OpenAPI spec alignment

***

All published OpenAPI specs were aligned with the actual codebase versions:

| Spec           | Updated to    |
| -------------- | ------------- |
| Ledger         | v3.5.0        |
| CRM            | latest stable |
| Fees Engine    | latest stable |
| Access Manager | latest stable |

## Impact

***

This documentation update includes information teams should review before changing the affected integration or deployment.

## What you need to do

***

<Steps>
  <Step>
    Review new Ledger Settings, Balance History, Transaction Routing, filters, and error documentation before your next Midaz integration change.
  </Step>
</Steps>

### Deadline

Before your next related integration, deployment, or upgrade change.

### Why

The public documentation was updated to reflect Cycle 6 API behavior and endpoint coverage.