
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 thechecking_accounts_balancestream, 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
financesstream. 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.
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.API Limitations
The Omie API enforces strict rate limits to prevent excessive usage. To avoid triggering Omie’sMISUSE_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
Activity Types
Activity Types
Attachment Types
Attachment Types
Banks
Banks
Card Brands
Card Brands
Categories
Categories
Checking Account Types
Checking Account Types
CNAE
CNAE
Countries
Countries
Departments
Departments
Document Types
Document Types
DRE
DRE
Installments
Installments
Subscriber Types
Subscriber Types
Task Types
Task Types
Transaction Origins
Transaction Origins
Transfer Purposes
Transfer Purposes
Users and Personnel
General Users
General Users
Users (CRM)
Users (CRM)
Sellers
Sellers
Clients and Companies
Clients
Clients
Companies
Companies
Projects
Projects
Financial Management
Checking Accounts
Checking Accounts
Checking Accounts Balance
Checking Accounts Balance
Checking Accounts Summary
Checking Accounts Summary
Checking Accounts Transfers
Checking Accounts Transfers
Bills (Accounts Payable)
Bills (Accounts Payable)
Bills Attachments
Bills Attachments
Receivables (Accounts Receivable)
Receivables (Accounts Receivable)
Titles
Titles
Deleted Titles
Deleted Titles
Finances
Finances
Finances Summary
Finances Summary
Quotes
Quotes
PIX
PIX
Tasks
Tasks
Tasks
Inventory
Inventory Adjustments
Inventory Adjustments
Inventory Movements
Inventory Movements
Products and suppliers
Products Summary
Products Summary
Supplier Products
Supplier Products
Orders and Services
Orders (Sales Orders)
Orders (Sales Orders)
Order Services
Order Services
Implementation Notes
API Limits & Performance
- Inventory Movements: The Omie API (
ListarMovimentoEstoqueendpoint) 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_inicialandd_periodo_finalfields in thechecking_accounts_balancestream 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 thelast_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.