We build ODXProxy and ODXPilot: tools for developers and teams who work with Odoo through its API.
A JSON-RPC 2.0 gateway in front of Odoo. Your app sends one request shape to ODXProxy, with the target
Odoo instance's credentials carried per request, and gets one response shape back, with errors mapped to
documented codes. v1 speaks Odoo's /jsonrpc (execute_kw) API, the only way to reach Odoo 18 and older.
v2 speaks Odoo's JSON-2 API for Odoo 19 and later, the only option on Odoo 22+. Both use the same x-api-key
header and envelope.
- Docs: odxproxy.io/docs · Getting started · API versions
- Official SDKs: Python · JavaScript / TypeScript · .NET · PHP · Java / Kotlin · Swift
- Claude Code skills for building Odoo apps on ODXProxy
An AI assistant for day-to-day Odoo administration. Ask in plain language. Approve before it changes. Answers come from live Odoo data. Every proposed change follows one of your own written procedures (SOPs) and shows up as a plan card that a person approves. Permissions are enforced in code, not in the prompt, and nothing is ever deleted. ODXPilot reaches Odoo only through ODXProxy.
- What ODXPilot is · Docs
- Install with one command via terrakernel/odxpilot-install. Requires Docker. You also need an ODXProxy licence (ask us), an Odoo user API key, an LLM key or your own model server, and preferably a test database.
Long-form guides on the odxproxy.io blog:
- Odoo API error handling: codes, retries and the 200 trap
- How to authenticate to the Odoo API
- Odoo domain filters: every operator, with examples
- Odoo 19 vs Odoo 20: what changed for developers
- Odoo XML-RPC is deprecated: migrating to the JSON-2 API
- odxbrain-corpus: audited Odoo model descriptions and version facts (CC0)
- tk-squeeler: Odoo addon to run raw SQL through the external API, with read/write groups and an audit log
- tk-mdpos · dnssense · tk-rand-core