Skip to main content
Omie is a comprehensive business management platform designed for Brazilian companies. It provides integrated tools for ERP, CRM, financial management, and business operations to help companies streamline their processes and improve efficiency.

Configuring Omie as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Omie option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need your Omie App Key and App Secret for this connection. You can find these credentials in your Omie integrations settings. Check Omie’s documentation to discover where you can find the App Key and App Secret for the connection.
  • App Key: Your application key for the Omie API.
  • App Secret: Your application secret for the Omie API.
  • Start Date: The earliest record date to sync.
  • Fetch daily account balances: (Default: false) Whether to fetch the checking_accounts_balance stream, which contains daily balance data per checking account. This stream makes one API request per account per day since the start date and can significantly slow down the first sync depending on the date range and number of accounts. Disabled by default for new connections.
  • Finance filter (advanced, optional): Use this filter to extract only the transactions of the specified category types in the finances stream. Allowed values: CP, CR, CPCR, BX, BXCP, BXCR, CC, CCE, CCS, CCT, PV, POS, PPV.

2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. Omie provides comprehensive business data including clients, finances, projects, and more.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data.
    • Full table: every time the extraction happens, we’ll get the current state of the data.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. Optionally, you can determine when to execute a full sync. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button.
For you to be able to see it on your Catalog, you need at least one successful source run.

API Limitations

The Omie API enforces strict rate limits to prevent excessive usage. To avoid triggering Omie’s MISUSE_API_PROCESS block (which restricts API access, usually for 5 minutes), the connector implements a built-in pacing mechanism with a 10-second delay between pagination date windows. If the API does block a request due to high consumption, the connector will gracefully pause extraction for the duration requested by Omie and then automatically retry. This ensures that large extractions and historical syncs complete reliably.

Streams and Fields

Below you’ll find all available data streams from Omie, their corresponding endpoints and fields:

Stream to Endpoint Mapping

Available Streams and Fields

Reference Tables

Reference table containing activity types (Tipos de Atividade).
Reference table containing attachment file types (Tipos de Anexo).
Reference table containing bank information and configurations.
Reference table containing card brands (Bandeiras de Cartao).
Reference table containing financial and operational categories.
Reference table containing checking account types (Tipos de Conta Corrente).
Reference table containing CNAE codes (Codigo Nacional de Atividades Economicas).
Reference table containing countries (Paises).
Reference table containing departmental organization structure.
Reference table containing document types (Tipos de Documento).
Reference table containing DRE structure (Demonstracao do Resultado do Exercicio).
Reference table containing installment configurations (Parcelas).
Reference table containing subscriber types (Tipos de Assinante).
Reference table containing task types (Tipos de Tarefa).
Reference table containing transaction origins (Origem de Lancamento).
Reference table containing transfer purposes by bank (Finalidades de Transferencia).

Users and Personnel

Stream containing general system users (Usuarios - Modulo Geral).
Stream containing CRM user information.
Stream containing seller/salesperson information.

Clients and Companies

Stream containing customer and client information from your Omie account.
Stream containing company and organization information.
Stream containing project information for tracking and management.

Financial Management

Stream containing bank account information and configurations.
Stream containing account balance information and statements.
This stream is only fetched if the Fetch daily account balances configuration is enabled. Fetching it may significantly slow down the first sync.
Stream containing a summary list of checking accounts (ListarResumoContasCorrentes).
Stream containing account transfer and transaction information.
Stream containing accounts payable and bill information.
Child stream of Bills containing file attachments associated with accounts payable.
Stream containing accounts receivable information.
Stream containing financial titles with detailed payment information.
Stream containing deleted financial titles (PesquisarExcluidos).
Stream containing comprehensive financial movement data.
Stream containing financial summary by day.
Stream containing quote and budget information by month.
Stream containing PIX payment information.

Tasks

Stream containing tasks (Tarefas).

Inventory

Stream containing inventory stock adjustments (Ajustes de Estoque).
Stream containing inventory movements (Movimento de Estoque).

Products and suppliers

Stream containing a summary list of registered products (ListarProdutosResumido).
Stream containing products per supplier (ListarProdutoFornecedor — produtos por fornecedor).

Orders and Services

Stream containing sales orders (Pedidos de Venda).
Stream containing service orders (Ordens de Servico — ListarOS).

Implementation Notes

API Limits & Performance

  • Inventory Movements: The Omie API (ListarMovimentoEstoque endpoint) has an undocumented volume limit where it silently returns empty results (“no records for this page”) instead of an error if the requested date range is too wide (often over 9-10 months or periods overlapping bulk imports). To prevent data loss, the connector automatically splits queries into narrower monthly windows.
  • Rate Limiting: Omie may block the API for 5 minutes (“consumo indevido”) if endpoints are hit too many times in quick succession. The connector addresses this by automatically pacing window transitions (adding delays between paginated requests) to safely stay under the threshold.

Checking Accounts Balance API Behavior

  • Calendar Dates: The d_periodo_inicial and d_periodo_final fields in the checking_accounts_balance stream are returned as pure calendar dates (YYYY-MM-DD) without a time component. This prevents timezone shifts when the data is processed by downstream systems.
  • Forecast Balances: The stream includes forecast balances (n_saldo_anterior_previsto, n_saldo_atual_previsto, n_saldo_prev) which account for unreconciled entries in the period.

Incremental Syncs and Replication Keys

For incrementally synced streams such as Bills, Bills Attachments, Checking Accounts Transfers, and Receivables, the connector uses the last_updated_at timestamp as the replication key. If a record has never been modified and lacks a modification timestamp (dAlt / hAlt), the connector automatically falls back to the creation timestamp (dInc / hInc) to ensure data is reliably captured during the incremental sync.

Data Quality and Fallbacks

The Omie API can sometimes return empty or zeroed dates (e.g., 00/00/0000) or malformed times. The connector gracefully handles these cases by emitting a null replication key when no valid date is present, and by defaulting to 00:00:00 (midnight) when the time is missing or unparseable. This prevents extraction failures caused by invalid timestamp formats.

Skills for agents

Download Omie skills file

Omie connector documentation as plain markdown, for use in AI agent contexts.