Skip to main content
This guide organizes fields used across the Lerian ecosystem into a single reference. It supports the engineering teams that work with Midaz, its embedded CRM and Fees Engine components, Flowker, Identity, Pix, Auth, Reporter, and related plugins. This dictionary helps you validate payloads, improve interoperability, simplify QA, and accelerate integration development.

​
Why this dictionary matters

New features, plugins, and versions bring new fields and behavior. This dictionary centralizes all definitions, so you can see how our products communicate with each other. Use it to:
  • Build integrations with confidence
  • Reduce ambiguity across workflows
  • Validate payload structures
  • Support QA, observability, and debugging
  • Accelerate onboarding for new developers

​
How to use this page

Each section groups fields by semantic categories. Every field includes:
  • Field name
  • Description
  • Where it is used across Lerian products
If you work with a specific product, open the dictionary page for that area, listed under Structure of the dictionary below.
For strict schema validation, always check the official OpenAPI specifications. Those files reflect the exact structure required by each endpoint.

​
Before you explore

This dictionary follows consistent conventions across all products.
  • Dates use ISO 8601 or RFC3339 formats
  • UUIDs follow v4 formatting
  • Pix fields follow BACEN standards
  • Workflow fields follow Flowker’s runtime and authoring semantics
  • Fees Engine fields reflect the latest v2 model
  • Metadata is always a flexible key-value
If your integration uses sensitive operations like Pix, Identity, or Fees Engine, verify behavior and accepted formats directly in the product APIs. Some fields behave differently depending on the execution context.

​
Structure of the dictionary

The dictionary has the following categories:

Core fields

Essential fields shared across all Lerian APIs, including identifiers, timestamps, pagination, and audit metadata.

People & Organizations

Fields that describe individuals, companies, users, groups, and organizational structures.

Financial data

Fields related to banking details, Pix operations, financial transactions, QR Codes, and operational limits.

Authentication & Security

Fields used for authentication, authorization, OAuth2 flows, webhook validation, and system health monitoring.

Workflows & Reporting

Fields related to workflow orchestration (Flowker), reporting (Reporter), fee calculations, and error handling.

Tracer

Fields for transaction validation, rules, spending limits, and decision responses.

Pix operations

Fields for Pix dispute resolution: claims, infraction reports, refund requests, and fraud markers.

Ledger operations

Fields for balances, transaction routes, operation routes, and metadata indexes.