Odoo integration consultant: connecting Odoo and moving to JSON-2.

Odoo's External RPC API documentation, read in November 2026, says the /xmlrpc, /xmlrpc/2 and /jsonrpc endpoints are deprecated and names External JSON-2 as the replacement. The db service is listed as removed in Odoo 20 (autumn 2026) and Online 19.1 (winter 2025). The common and object services are scheduled for removal in Odoo 22 (autumn 2028) and Online 21.1 (winter 2027).

Note the gap between those last two dates. A company on Odoo Online reaches the removal earlier than one on a self-hosted version. Scripts and connectors using the old endpoints keep working until then, and a version upgrade is the moment they stop.

Odoo's 19.0 developer documentation describes JSON-2. The 18.0 external API page we read describes XML-RPC only, so a company on an older version has to plan the upgrade and the integration change together.

Odoo's documentation, read in November 2026, says access to data through the external API is only available on Custom plans, and is not available on One App Free or Standard. Its pricing page agrees, and notes that calls Odoo itself makes to services such as payment providers and carriers are part of the standard plan. Custom is also the plan that allows Odoo.sh or on-premise hosting.

We check this first, because a company on Standard cannot connect outside software to Odoo's data until it changes plan. The per-user cost of that change belongs in your budget for the project. Odoo shows prices by region, so we read yours rather than quote one here.

The change is more than a new address, because several behaviours differ. These points come from Odoo's 19.0 documentation, read in November 2026:

• Requests are JSON posts to a model and method URL under /json/2/, with arguments passed by name.
• An API key travels as a bearer token in the Authorization header, and the database goes in an X-Odoo-Database header when needed.
• Keys cannot last longer than three months, so an integration needs a rotation routine and an owner for it.
• Each call runs in its own SQL transaction and calls cannot be chained into one, so multi-step writes need a plan for partial failure.
• Odoo's own access rights apply, and the documentation recommends dedicated bot users over personal accounts.

We connect Odoo to other systems. Orders from Shopify, deals from HubSpot, invoices and payment status from Stripe, and alerts in Slack are typical connections, through direct JSON-2 calls or with n8n or Make in the middle. Before relying on any connector we check which endpoint it calls, and we list every existing script and its endpoint before a migration.

SBD has no published case study on Odoo and has not published a JSON-2 integration. The closest published work is an enquiry and quotation platform that works with SAP for an industrial distributor, and a sales channel inventory sync. We would test against a copy of your database and show you the results before anything touches production.

Outside integration makes sense when another system has to stay in place and both need the same orders, customers or stock. It is often the wrong answer in these cases:

• An Odoo app or setting already covers the need. Turning it on costs less than maintaining a sync.
• You need Odoo implemented, customised or your accounting set up. An Odoo partner is the right firm for that, and we can work alongside them on the connections.
• You are on Standard and the integration is worth less than the plan change.
• Your processes are still changing weekly, so a sync would keep breaking.

Every engagement starts with an Automation Audit at $500, credited in full to your build. We confirm your plan and version, list what touches Odoo today and tell you what needs to move and by when. Workflows start at $1,500 and multi-module systems at $5,000, as a fixed price set after the audit. Bot users, keys and code stay in your accounts.