Odoo external API access: what it really costs.

That's a doubling of your entire licence bill, across every user, to connect one system to another.

What the documentation actually says

From Odoo's External API reference, unchanged across versions 16 through 19:

It applies to both endpoints:

• XML-RPC — the long-standing interface, /xmlrpc/2/common and /xmlrpc/2/object, using execute_kw
• JSON-2 — newer, POST /json/2/<model>/<method> with a Bearer API key. More pleasant to work with, same commercial gate.

The arithmetic

25 people, US list, renewal rates, August 2026:

That's the cost of the API, and it scales with headcount rather than with integration usage. A 60-person business pays roughly $21,500 a year more for the same single integration.

Custom does include other things — Odoo Studio, multi-company, self-hosting and Odoo.sh eligibility. If you need those anyway, the API comes along for free. If the API is the only reason you're on Custom, you're paying a per-seat price for a machine-to-machine feature, which is an odd shape for a bill.

What this blocks on Standard

Anything that talks to Odoo from outside:

• A warehouse or 3PL system pushing stock movements
• A marketplace or channel integration you built rather than bought
• A BI or reporting tool reading Odoo data
• A custom customer portal
• Middleware syncing to another business system
• Scripts that import, export or reconcile on a schedule
• AI assistants — connecting Claude, ChatGPT or anything else through Odoo's API

The last one is why this question has got much more common in the past year.

An honest complication

Reports from developers suggest the restriction isn't uniformly enforced. There are documented cases — including a May 2026 thread on Odoo's own forum — of databases on the One App Free plan successfully authenticating and reading data through both XML-RPC and JSON-2, despite the documented limit.

Two things follow, and the second matters more.

First: if you're testing on a free or Standard database and the API works, that isn't confirmation you're entitled to it. It may be inconsistent enforcement rather than permission.

Second, and this is the real point: building a production integration on an undocumented, unenforced allowance is a bad bet. The documented position is the one Odoo can enforce at any point, with no notice required, because the docs have said so for four major versions. If your operations depend on that integration, an enforcement change is an outage you can't fix by writing code.

Budget for Custom, or use one of the routes below.

The two ways around it

1. Odoo Community

Self-hosted Community has full external API access with no licence gate, because the restriction is a commercial term attached to Odoo Online plans, not a technical limitation of the software.

So the free edition is less restricted than Enterprise Standard on this specific point. That's genuinely unusual and worth sitting with if you're currently choosing between them: a business whose main requirement is integration may find Community both cheaper and more capable for that purpose.

What Community costs you elsewhere — Studio, official Odoo support, Odoo.sh, the Enterprise-only apps — is in Odoo Community vs Enterprise. It's a real list and it decides the question for some businesses.

2. Don't leave Odoo in the first place

The external API exists so external software can reach in. But a module running inside Odoo isn't external — it calls the ORM directly, in-process, and no external-API entitlement applies.

That's how our Odoo MCP server works. It runs inside your Odoo, so connecting Claude, ChatGPT, Gemini, Copilot or Cursor doesn't touch the external API and doesn't need the Custom plan. It also executes as the real signed-in user with their existing permissions, which is a better security position than an API key with whatever rights the account behind it holds.

If you're weighing an AI integration against a conventional one, MCP vs the Odoo API covers where each is genuinely the right tool — API for scheduled syncs and batch work, MCP for conversational and agentic access.

What to do, depending on where you are

Budgeting a new Odoo deployment with integrations planned: price Custom, not Standard, or plan on Community. Discovering this after signing a Standard contract is a bad week. Full picture: what an Odoo implementation actually costs.

On Standard and just hit the wall: three options — upgrade to Custom, move to Community, or move the integration inside Odoo as a module. Which is right depends on whether Studio and the Enterprise apps matter to you independently.

Choosing between Community and Enterprise, integration-heavy: this may be the deciding factor, and it points the opposite way to most advice you'll read.

Only wanting AI access: you don't need the external API at all. An in-Odoo MCP module covers it on any edition or plan.

Where we sit

We host standard Odoo Community at $150/month for up to 25 people or $450/month unlimited — full external API access included, because Community has it, plus every module we've built at no extra cost including the MCP server.

For a 25-person business needing API access, that's $1,800 a year against roughly $18,300 for Odoo Custom. The honest caveat, same as everywhere else on this site: Community means no Studio, no official Odoo SA support, no Odoo.sh, and no Enterprise-only apps. If you need those, pay Odoo — and you'll have the API anyway.

See the pricing · Flat-fee Odoo hosting

Official documentation

• Odoo 19 External API (JSON-2)

The rest of the cluster