Connecting an app to Odoo

Odoo is one of the few ERPs whose external API is publicly documented and usable without going through a partner. That is good news when you want to connect a business app, a customer portal or a field tool. But two things change the picture in 2026: the plan you need and the move to a new API. Here is what the official documentation said when I checked it in October 2026.

What Odoo’s API allows

Since Odoo 19, the JSON-2 external API documentation describes a single endpoint: each call targets an Odoo model (contacts, orders, invoices, products) and a method (read, search, create, update).

In practice, an app can read customers and products from Odoo, create orders or service calls in it, and fetch invoice status, with the same checks as if a user did it by hand. That is an advantage: the rules already configured in Odoo keep applying.

To avoid polling Odoo every minute, automation rules can send a webhook notification to your app when a record changes, and can trigger actions from an external event.

Odoo module or separate app

That is the real question before talking about connections.

• An Odoo module fits when your users already work in Odoo and a function close to the standard is missing: a field, a screen, a calculation.
• A separate app connected through the API fits when users have no Odoo license (customers, partners, seasonal staff), when the interface has to be very simple or mobile, or when the need goes beyond what an ERP covers.

My work is custom web applications. If your need clearly calls for a module, an Odoo partner will be better placed, and I will tell you so. The page customize Odoo or build custom software? goes into this choice.

Budget and timeline

Amounts exclude VAT and cover a first version running in production. The connection matches the “connection to other tools” building block in my pricing ($2,300 (€2,000)excl. VAT), plus the work specific to your flows.

The estimator gives you a range in one minute. The quote becomes fixed after scoping.

Good practices

1. A dedicated technical user. The app connects with an account that has minimal rights, never an administrator’s. Odoo’s documentation also recommends dedicated users for integrations.
2. One source of truth per piece of data. Odoo for invoicing and stock, the app for what it creates. They must never both edit the same field.
3. Grouped operations. Since every call stands alone, a booking or a payment should go through a method that does everything at once, not a chain of calls.
4. A log of exchanges. Every send, every error and every retry is recorded and searchable.

When this is not the right approach

If you are on the Standard plan and the need is modest, upgrading to Custom for a single connection can cost more than the problem it solves. A scheduled export or a module from the Odoo Apps store may be enough.

And if all your teams work in Odoo, a separate app adds one more tool to learn. In that case, invest in configuration or a module, not in an external custom app. The guide custom app vs. SaaS helps frame the question.

Where to start

1. Check your Odoo plan and version: online, on Odoo.sh or self-hosted.
2. List the users outside Odoo and what they re-enter today.
3. A 30-minute call to confirm feasibility.
4. Scoping (1 to 2 weeks): flows, Odoo models involved, fixed quote.
5. Development in batches against a test Odoo database, then go-live.

If the app also needs to talk to your online store, see connecting your online store to your ERP. My approach is described on the business apps page.