Guide · Last verified August 8, 2026
If you run Odoo Online and want to connect a BI platform, an automation service, or an AI assistant such as Claude or ChatGPT, your subscription decides whether that is possible. Odoo documents External API access as available on the Custom plan.
Officially, no. Odoo's External API documentation states that access through the External API is available only on Custom pricing plans, and is not available on the One App Free or Standard plans. The most important distinction to hold on to is that Odoo Online Custom gives you External API access but still does not allow arbitrary server-side Python modules. That is why integrations built for Odoo Online run outside Odoo and talk to the database through the supported External API, instead of requiring a module to be installed.
| Odoo environment | External API | Custom Python modules | Suitable for external AI integrations |
|---|---|---|---|
| One App Free — Odoo Online | No, officially | No | No, for API-dependent integrations |
| Standard — Odoo Online | No, officially | No | No, for API-dependent integrations |
| Custom — Odoo Online | Yes | No | Yes |
| Odoo.sh | Yes | Yes | Yes |
| On-premise / self-hosted | Yes | Yes | Yes |
Seeing an API-key option — or even making a limited API request succeed — should not be treated as proof that your subscription includes supported External API access. There are community reports of calls succeeding on plans that do not officially include it. Designing a production integration around behavior that may not be part of your supported entitlement means it can stop working without that being a fault you can raise. Confirm against your subscription instead.
Buying the Custom plan does not mean you can upload a third-party Python module to your yourcompany.odoo.com database. Odoo documents Odoo Online as incompatible with custom server-side modules and with ordinary Odoo Apps Store modules — on Custom too. Custom unlocks External API access and Odoo Studio, not module installation.
| Capability | Odoo Online — Custom | Odoo.sh | On-premise |
|---|---|---|---|
| Hosted by Odoo | Yes | Yes | No |
| Managed Odoo platform | Yes | Yes | No |
| External API | Yes | Yes | Yes |
| Odoo Studio | Yes | Yes | Depends on edition |
| Install arbitrary Python modules | No | Yes | Yes |
| Install a native third-party MCP module | No | Yes | Yes |
| Use an external API-based MCP gateway | Yes | Yes | Yes |
| Full server / code access | No | Yes | Yes |
XML-RPC has carried Odoo integrations for years and still works today. Odoo has now formally deprecated the /xmlrpc, /xmlrpc/2, and /jsonrpc external RPC endpoints.
XML-RPC is not suddenly unusable in Odoo 19, but new architecture should account for its removal.
Odoo 19 introduces JSON-2 as the replacement. Requests use endpoints structured as /json/2/<model>/<method> and authenticate with an API key as a bearer token. For long-lived integrations, JSON-2 belongs in the migration roadmap.
Use the Odoo Online MCP Gateway. It runs outside the SaaS database and bridges an MCP client to the Odoo External API. No server-side module is installed.
AI client → MCP Gateway → Odoo External API → Odoo Online
Use the MCP Server for Odoo, because those environments allow custom server-side modules. Add the governance layer where writes need recording.
AI client → MCP Server module → Odoo
Keeping these separate prevents the most common and most expensive mistake in this category: buying an Odoo module and then discovering Odoo Online will not allow it to be installed.
Confirm your subscription. For an External API-based integration, verify the database is on the Custom plan.
Use a dedicated Odoo user. Give the integration only the business permissions it actually needs.
Review access rights and record rules. API requests execute in the context of an Odoo user, so user permissions decide what is reachable.
Protect and rotate credentials. Treat an Odoo API key like a password.
Start with limited access. If the AI only needs to analyze data, do not grant create, write, or delete permissions.
Test with non-critical records first. Verify what the integration can reach before connecting sensitive production workflows.
According to Odoo’s official pricing and developer documentation, no. Supported External API access is included with the Custom plan and is not included with the One App Free or Standard plans. If your integration depends on Odoo’s External API — which includes analytics tools, automation platforms, data sync services, external AI agents, and API-based MCP gateways — the Custom plan should be treated as a requirement.
No, and this is the most common way teams get caught out. Seeing an API-key field, or even making a limited API request succeed, is not proof that your subscription includes supported External API access. There are community reports of calls succeeding on plans that do not officially include the entitlement. Building a production integration on undocumented behavior means it can stop working without that being a bug you can raise. Confirm the entitlement against your subscription rather than testing for it.
If the Claude integration depends on Odoo’s External API, yes. An API-based MCP gateway such as the KSROlabs Odoo Online MCP Gateway requires supported External API access, which Odoo currently associates with the Custom plan. The requirement comes from Odoo, not from Claude or from the gateway.
For an External API-based ChatGPT or MCP integration, yes. The relevant requirement is the Odoo External API rather than anything on the ChatGPT side. The same applies to any external service that reads Odoo data over the API.
Not if the MCP server requires a custom server-side Python module. Odoo Online does not support arbitrary custom Python modules or ordinary Odoo Apps Store modules, and buying the Custom plan does not change that. Custom unlocks External API access and Odoo Studio, not module installation. Use an external API-based gateway instead, or move to Odoo.sh or self-hosting if you need a native module.
No, and the word “Custom” makes this confusing. Both are hosted by Odoo and both give you External API access and Odoo Studio. The difference is code: Odoo.sh lets you install arbitrary Python modules, including a native MCP module, and gives you server access. Odoo Online Custom does neither. Choose Odoo.sh when the implementation needs custom modules or server-side development; choose Odoo Online Custom when you want to stay on Odoo’s fully managed SaaS and connect approved external services through the API.
It is deprecated but not yet removed. Odoo has formally deprecated the /xmlrpc, /xmlrpc/2, and /jsonrpc external RPC endpoints, and currently schedules removal for Odoo 22 in autumn 2028 and Odoo Online 21.1 in winter 2027. XML-RPC is not suddenly unusable in Odoo 19, but any long-lived integration architecture should account for its eventual removal. Odoo 19 introduces the External JSON-2 API as the replacement, using endpoints structured as /json/2/<model>/<method> with an API key as a bearer token.
Tell us your Odoo URL and hosting and we will confirm whether an API-based integration is supported before you buy anything.
Ask us to check your instance →