Omie API: what you can do and how to use it with AI agents
The Omie API exposes the main records and transactions of this Brazilian ERP, such as customers, products, sales orders, finance and tax invoices (notas fiscais). Companies and integrators use it to link Omie to e-commerce, CRM and internal routines. Access uses app keys generated in the Omie account itself.
What the Omie API offers
Records
Customers, suppliers, products, services and financial categories.
Sales and purchase orders
Creating, querying and tracking orders and service orders.
Finance
Accounts payable, accounts receivable, entries and checking accounts.
Tax invoices
Querying and issuing tax documents linked to orders.
Inventory
Stock position and product movements.
Webhooks
Notices of account events, such as records being added or changed.
How to access the Omie API
- With your company’s credentialsCalls use a pair of app keys (app key and app secret) generated in the developer panel of the Omie account.
- The API has request limits per period; batch routines should be spaced out.
- Prefer a user or app used only by the integration, to separate what the agent did.
- Test first in a test company, if you have one, before going live on real finance.
Official documentation: developer.omie.com.br
What an iTeam agent does with the Omie API
Receivables kept current
The agent lists overdue receivables in Omie, sends reminders to the customer and records the negotiation; a manual write-off happens only with finance approval.
CRM order straight into the ERP
When the salesperson marks the deal as won, the agent creates the sales order in Omie with the customer and items checked and warns if a record is missing.
Checking entries
The agent compares the bank statement with Omie entries and flags what has no category or is unreconciled, for the accountant to review.
Weekly finance summary
Every Monday the manager receives the projected balance, the week's payables and the largest overdue items, pulled straight from the ERP.
From the credential to the agent at work, with approval
Generate the keys in Omie
In the Omie developer portal, create the integration app and copy the company's app key and app secret.
Register them in the vault and limit the scope
The keys go in the iTeam vault; you define which agents read finance, which create orders and which actions need approval.
Validate in a controlled routine
The agent starts with reading and reports; writing to orders and finance is enabled gradually, with every action recorded in the audit trail.
Ready-made AI teams that use Omie
Bank reconciliation team
Bank lines, Stripe payouts and ledger entries are matched each morning. You only see what did not match, with a reason.
Accounts payable team
Invoices arrive by e-mail and in shared folders. The team reads them, checks them and lines them up for your approval before the due date.
Cash flow forecast team
Every week the projection is rebuilt from your books, open invoices and bills, with a plain note on what changed and why.
Management reporting team
Revenue, margin, pipeline and cash in one report, built from your systems, with a short note on what changed and why.
Inventory planning team
Stock, sales and lead times are checked every day. You get a reorder list per SKU and a warning about what is not selling.
Questions about the Omie API
Is the Omie API free?
In general, the API is part of the Omie subscription and has no separate charge for customers using it with their own account. Confirm the terms of your plan with Omie.
Do I need to write code to use the Omie API with iTeam?
Not necessarily. iTeam's HTTP tool learns the methods from the Omie documentation and the deployment team sets up the routines with you.
Can the agent issue tax invoices on its own?
It can be configured to, but we recommend starting with human approval on every issue and automating only repetitive cases once they are validated.
