Skip to Content
This question has been flagged
1 Reply
450 Views
Avatar
santosh

We are currently working with the Odoo Community Edition and have reached a stage where the default Odoo backend no longer meets our UI/UX and workflow requirements. To better align with our needs, we are planning to build a custom frontend interface in React.


As part of this effort, we are evaluating two potential integration options with Odoo:

  1. JSON-RPC (native and modern integration method in Odoo)
  2. REST API (via community modules such as rest_api from OCA or a custom-built solution)

Our key requirements include:

  • Seamless integration with a custom-designed frontend (likely using React )
  • Access to standard Odoo models such as sale.order, res.partner, stock.picking,Inventory,invoice etc.
  • Secure and manageable authentication workflows
  • Good performance with consideration for future upgrades and maintainability

We would greatly value your input based on real-world experience:

  • Which integration approach (JSON-RPC or REST) has worked better in your custom frontend projects?
  • What trade-offs or limitations have you encountered with either method?
  • In your experience, is the community REST API module production-ready and reliable?
  • Any insights, pros/cons comparisons, or example use cases would be extremely helpful.

Thank you in advance for your support and guidance. Looking forward to your recommendations.

Avatar
Discard
Avatar
Christoph Farnleitner
Best Answer

My take on your questions would be

Which integration approach (JSON-RPC or REST) has worked better in your custom frontend projects? And What trade-offs or limitations have you encountered with either method?

In general, and especially under considering 'Seamless integration' and 'Access to standard Odoo models', JSON (or XML)-RPC due to the fact that basically all of Odoo will be available to you already. REST-API from OCA (fastapi) will require you to define every single call adding extra work and a level of complexity for upgrades. This is also true when you want an 'open' integration not limiting yourself to a specific use case or use in a single project.
OCA's fastapi in my opinion shines most when you have a specific task at hand with a limited scope that requires heavy mapping or has an emphasis on detailed documentation.
fastapi could have you end up with a messy list of dependencies or, when considering a more modular approach, a huge list of tiny modules all just defining single routes.

The better choice definitely depends on what all you need access to from Odoo.

In your experience, is the community REST API module production-ready and reliable? Yes

Avatar
Discard