> ## 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.

# July 2026

> Documentation updates and release notes published in July 2026 for Midaz, plugins, and platform tools, grouped by required customer action.

Updates are grouped by required customer action. Product filters show only the areas that affect your integration. See [News](/en/news/news) for impact definitions.

## No action

***

<Update label="July 7th, 2026" tags={["Matcher"]}>
  ### [Matcher v4.3.0 — AI-assisted ingestion, discovery connectors, and Console rebrand](/en/news/2026/july/matcher-v430)

  **What changed**

  Matcher adds AI-assisted document extraction, field-mapping proposals, and match-rule suggestions — each with a human-in-the-loop review step before anything is applied. A new discovery-connector platform onboards sources from aggregators (Pluggy, Belvo), file formats (CNAB240, CNAB400, OFX, camt.053 preview), and SFTP. API error responses are now a consistent problem shape (`type`, `title`, `status`, `detail`). The Console adopts the new ink-blue theme with refreshed navigation and breadcrumbs. Seven customer-facing reliability fixes are included.

  **Who is affected**

  Teams using Matcher for reconciliation — operators uploading and mapping statements, teams building match rules, and integrations that parse Matcher API error responses.

  **What you need to do**

  Review the new AI extraction, mapping, and rule-suggestion flows and assign an owner to the approval step. Explore the discovery connectors if you onboard sources via aggregators or files. Confirm that any code parsing Matcher error responses handles the new problem shape. No migration is required for existing integrations.
</Update>

<Update label="July 7th, 2026" tags={["Midaz"]}>
  ### [New reference: Receiving Midaz events — RabbitMQ vs Streaming Hub](/en/news/2026/july/receiving-midaz-events-guide)

  **What changed**

  A new reference guide, Receiving events from Midaz, documents the two supported ways to consume the Midaz event stream — binding your own queue directly to Midaz's RabbitMQ (AMQP 0-9-1) topic exchanges, or subscribing through Lerian's managed Streaming Hub (Webhook, Pull, SQS, RabbitMQ, or EventBridge) — with a side-by-side comparison to help you choose.

  **Who is affected**

  Teams integrating with Midaz that react to ledger events — reconciliation, notifications, downstream projections, and analytics — instead of polling the REST API, including both self-hosted deployments and external / SaaS integrators.

  **What you need to do**

  No migration is required. No endpoints, event schemas, or delivery behavior changed. Self-hosted teams should review the RabbitMQ direct section and self-hosted environment flags; external consumers should review the Streaming Hub section and pick a delivery transport.
</Update>

<Update label="July 9th, 2026" tags={["Platform"]}>
  ### [New documentation structure — journey-first navigation](/en/news/2026/july/documentation-information-architecture)

  **What changed**

  The documentation portal moves to a journey-first information architecture. Tabs now follow how you work — Fundamentals, Guides, API Reference, Platform, and Lerian Console — rather than splitting by product first. API Reference is regrouped by product, and product guides now cross-link to their matching API reference so you can move between a concept and its endpoints in one step. Every previous URL keeps working through redirects, so existing bookmarks and shared links resolve automatically to their new locations.

  **Who is affected**

  Anyone using the Lerian documentation portal — no product, API, or runtime behavior changes.

  **What you need to do**

  Nothing. Browse the new tabs at your own pace; old links redirect to their new locations. Update saved bookmarks whenever convenient — there is no deadline and nothing breaks if you don't.
</Update>

<Update label="July 9th, 2026" tags={["Midaz", "Pix", "Reporter", "Tracer", "Platform"]}>
  ### [Expanded API Reference — Pix — Direct via JD, the Midaz ledger, and Pix Automático](/en/reference/introduction)

  **What changed**

  The API Reference gains substantial new coverage — all of it documentation, with no product, endpoint, or runtime behavior change:

  * **Pix — Direct via JD** is published for the first time, with 97 operations rendered end to end.
  * The **Midaz ledger** reference is expanded with the holders and billing domains — 31 additional operations.
  * **Pix Automático** payer-side operations are added to the **Pix — Indirect via BTG** reference.
  * The former **CRM** reference is retired into the Midaz ledger section, where holders and related parties now live. Previous CRM reference links redirect automatically.
  * The **Reporter**, database connections, **Access Manager**, and **Tracer** references are refreshed to match their current operations.

  **Who is affected**

  Anyone browsing the Lerian API Reference — in particular teams integrating Pix via JD or BTG, teams working with Midaz holders and billing, and anyone who had bookmarked CRM reference pages. These operations were already part of the products; the reference now renders them.

  **What you need to do**

  Nothing. No endpoints, request or response schemas, authentication, or delivery behavior changed — these are documentation-only updates, so there is nothing to change in your integration. Old CRM reference URLs redirect to their new Midaz ledger locations automatically; update saved bookmarks whenever convenient.
</Update>

## Product index

***

| Product area | July updates                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Matcher**  | v4.3.0 adds AI-assisted document extraction, mapping proposals, and match-rule suggestions (all with human-in-the-loop review), a new discovery-connector platform (Pluggy, Belvo, CNAB240/400, OFX, SFTP, camt.053 preview), standardized API error responses, an ink-blue Console rebrand with refreshed navigation, and seven reliability fixes.                                                                                                                                                                                             |
| **Midaz**    | A new reference guide, Receiving events from Midaz, explains the two supported ways to consume Midaz ledger events — direct RabbitMQ (AMQP) exchange binding for self-hosted deployments, or the managed Streaming Hub for external / SaaS integrators — and how to choose between them. The ledger API reference is also expanded with the holders and billing domains (31 additional operations), and the former CRM reference is retired into the Midaz ledger section (holders and related parties) — old CRM links redirect automatically. |
| **Pix**      | The Pix — Direct via JD API reference is published for the first time (97 operations), and Pix Automático payer-side operations are added to the Pix — Indirect via BTG reference. Documentation only — no product or endpoint behavior changed.                                                                                                                                                                                                                                                                                                |
| **Platform** | The documentation portal moves to a journey-first information architecture — tabs organized by how you work, an API Reference regrouped by product, and redirects that keep every previous URL working. The database connections and Access Manager API references are also refreshed to match their current operations.                                                                                                                                                                                                                        |
| **Reporter** | The API reference is refreshed with the template-builder and deadline-notification operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Tracer**   | The API reference is refreshed with its reservation operations.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |