Odoo 19: the External JSON-2 API

With the release of Odoo 19, the ERP vendor takes a new step in openness and integration. The XML-RPC protocol, used for years to connect Odoo to other systems, is now officially replaced by the new External JSON-2 API.

This change may seem technical, but it is strategic: it gives Odoo integrators and user companies alike a modern, fast and secure gateway to interconnect their Odoo ERP with their other tools (e-commerce, logistics, finance, CRM, BI...).

👉 In short: with Odoo 19, Odoo integration projects become simpler, more reliable and less costly.

Why is Odoo abandoning XML-RPC?

For a long time, XML-RPC made it possible to link Odoo to third-party applications. But this technology showed its limits:

• Verbose: exchanges were heavy and hard to process.
• Aging: based on methods poorly suited to modern web standards.
• Limiting: complex handling of access rights and transactions.

👉 Consequence for companies: long, costly and sometimes fragile integrations.

With Odoo 19, the open-source ERP says goodbye to XML-RPC and adopts a modern API aligned with web standards: JSON-2.

The benefits of the External JSON-2 API

1. A universal, lightweight format: JSON

The new API is based on JSON, the standard format of the web and mobile applications. Simpler, more readable and faster.

👉 Business impact: connecting Odoo to an e-commerce site, a CRM or a BI tool becomes smoother and less costly.

2. A clear, standardized structure

The JSON-2 API is organized into dedicated services (common, database, object).

👉 Benefit: integrators work faster and projects are better controlled.

3. Stronger security

The old RPC sessions are replaced by secure API keys, easily generated and managed.

👉 Use case: a logistics provider can access only the delivery orders, without ever seeing your sensitive data.

4. Atomic transactions

Several actions can now be grouped into a single transaction.

👉 Concrete example: a sales order, its delivery and its invoice are validated together. If one step fails, nothing is saved → greater reliability.

5. Easier migration

Odoo provides a guide to migrate existing integrations from XML-RPC to JSON-2.

👉 Consequence: no need to rewrite everything; your investments are preserved.

6. Introspection and improved documentation

The API can be queried to discover its methods and parameters.

👉 For companies: fewer errors and less wasted time = faster projects and better-controlled budgets.

7. Increased performance and reliability

• Less technical overhead,
• Faster exchanges,
• Better management of rights and access.

👉 Direct impact: a smoother, more robust and more secure Odoo integration.

Comparison table

Concrete business use cases

1. E-commerce: real-time synchronization

An online store connected to Odoo can display always up-to-date stock levels and reduce stock-outs.

👉 Result: satisfied customers and fewer after-sales requests.

2. Logistics: better-connected partners

Thanks to API keys, carriers access delivery orders live, without exposing any other data.

👉 Result: a smoother and more secure supply chain.

3. Finance: automated reporting

Odoo's accounting data can feed Power BI or Qlik directly.

👉 Result: reliable, up-to-date dashboards with no double entry.

Tips for a successful transition

1. Inventory your existing integrations based on XML-RPC.
2. Migrate critical flows first (e-commerce, logistics, finance).
3. Test your exchanges to secure the switchover.
4. Train your teams on the new API.
5. Plan a coexistence phase between XML-RPC and JSON-2 for the duration of the transition.

Conclusion

With the External JSON-2 API, Odoo 19 takes a decisive step.

• For integrators: a modern, clear, fast and secure API.
• For companies: faster, more reliable and less costly Odoo integration projects.

By adopting JSON-2, Odoo confirms its ambition: to become a connected ERP fully aligned with modern web standards.