Updates are grouped by required customer action. Product filters show only the areas that affect your integration. See News for impact definitions.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.
Action required
TED: documentation aligned with v2.4.0
What changedThe public TED documentation now reflects version2.4.0, including transfer fields, webhooks, configuration, and error references.Who is affectedTeams integrating with the TED plugin, especially teams creating transfer requests.What you need to doReview InitiateTransferRequest and make sure transfer creation payloads include the required purpose field.Review recommended
Matcher: API reference aligned with v2.1.1
What changedThe public Matcher API reference now reflects the releasedv2.1.1 binary and Go DTOs, including fee-rule routes, schema names, fields, and error references.Who is affectedTeams using Matcher API documentation to implement or review integrations.What you need to doReview the updated documentation before your next Matcher integration change. No product behavior changed in this documentation update.Flowker: API reference cleanup and v1 endpoints registered
What changedThe public Flowker API reference no longer shows phantom health endpoints, and seven existing v1 endpoints are now visible in the documentation portal.Who is affectedTeams using Flowker documentation for API discovery or AI-assisted documentation search.What you need to doReview the newly visible v1 endpoints if you use Flowker. Keep operational health checks tied to internal documentation, not the public API reference.Access Manager: MFA and Provider documentation update
What changedThe public Access Manager API reference now includes missing MFA, Provider, and application-provider pages.Who is affectedTeams using Access Manager MFA, provider configuration, or application-provider links.What you need to doReview the new Access Manager pages if those capabilities are part of your roadmap. Existing integrations do not need a migration from this documentation update alone.Midaz: ledger list filters documented
What changedThe public Midaz Ledger API reference now shows previously missing filters for accounts, organizations, and account types.Who is affectedTeams querying Midaz accounts, organizations, or account types.What you need to doReview the updated list filters if your integration uses those endpoints. Existing integrations do not need a migration from this documentation update alone.CRM: identity reference context updated
What changedCRM-related identity documentation context was updated as part of the May API reference audit.Who is affectedTeams reading CRM documentation alongside identity-related API reference pages.What you need to doReview CRM together with the updated identity reference pages if your implementation depends on both areas. No CRM runtime behavior changed.No action
Reporter Console: operational guides and field references
What changedReporter Console documentation now has clearer operational guides, field references, Data Source journey guidance, API reference links, and aligned EN/ES/PT structure.Who is affectedOperators, administrators, implementation teams, and integrators using Reporter through Lerian Console.What you need to doNo migration is required. Review the updated Reporter Console documentation before onboarding operators or reviewing Reporter workflows.Lerian Console: Midaz Module documentation clarity
What changedThe Lerian Console documentation now has clearer Midaz Module navigation, an explicit setup path, sharper plugin and Fees Engine guidance, and aligned EN/ES/PT structure.Who is affectedOperators, administrators, implementation teams, and developers using Lerian Console to operate Midaz.What you need to doNo migration is required. Review the updated Lerian Console documentation if you operate or onboard operators to the Midaz Module.Midaz: account statement guide
What changedA new Midaz guide explains how to transform account operations into customer-facing account statements.Who is affectedTeams building statement experiences with Midaz account operations.What you need to doNo migration is required. Use the new guide when designing, implementing, or reviewing account statement views.Tracer: spending limit documentation update
What changedThe public Tracer documentation now explains the full spending limit model, including periods, scheduling fields, amount format, and validation timing.Who is affectedTeams reading Tracer documentation to understand spending limit configuration or validation behavior.What you need to doNo migration is required. Use the updated documentation when configuring or reviewing Tracer limits.Matcher: source documentation field correction
What changedThe public Matcher documentation now shows source payloads withoutfeeScheduleId.Who is affectedTeams reading Matcher documentation to configure reconciliation sources.What you need to doNo migration is required if your integration already works. Use Matcher fee rules for fee behavior instead of source fields.Flowker: operational endpoints removed from public reference
What changedFlowker health and version endpoints no longer appear in the public API reference.Who is affectedTeams reading the public Flowker API reference.What you need to doNo product behavior changed. Keep operational monitoring tied to internal runbooks or deployment documentation.Matcher: operational endpoints removed from public reference
What changedMatcher health, version, and readiness endpoints no longer appear in the public API reference.Who is affectedTeams reading the public Matcher API reference.What you need to doNo product behavior changed. Keep operational monitoring tied to internal runbooks or deployment documentation.Tracer: operational endpoints removed from public reference
What changedTracer health, version, and readiness endpoints no longer appear in the public API reference.Who is affectedTeams reading the public Tracer API reference.What you need to doNo product behavior changed. Keep operational monitoring tied to internal runbooks or deployment documentation.TED: operational endpoints removed from public reference
What changedTED liveness and readiness endpoints no longer appear in the public API reference.Who is affectedTeams reading the public TED API reference.What you need to doNo product behavior changed. Keep operational monitoring tied to internal runbooks or deployment documentation.Product index
| Product area | May updates |
|---|---|
| Access Manager | MFA, Providers, Application-Provider links, and Auth MFA login-flow documentation were expanded. |
| Console | Lerian Console documentation clarified for the Midaz Module, including setup path, plugin settings, Fees Engine package creation, and EN/ES/PT navigation parity. |
| CRM | CRM-related identity documentation context updated. |
| Flowker | Public API reference cleanup, v1 endpoint registration, and operational endpoints removed from the public reference. |
| Matcher | API reference alignment with released v2.1.1 behavior, source field correction, and operational endpoints removed from the public reference. |
| Midaz | Missing query parameters documented on ledger list endpoints and a new account statement guide published. |
| Reporter | Reporter Console documentation updated with operational guides, field references, Data Source journey guidance, API reference links, and EN/ES/PT language parity. |
| TED | Plugin documentation aligned with 2.4.0 and operational endpoints removed from the public reference. |
| Tracer | Full spending limit model added and operational endpoints removed from the public reference. |