migrate an odoo integration from the legacy xml-rpc/json-rpc api to the external json-2 api

domain: odoo.com/documentation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Note that the /xmlrpc, /xmlrpc/2, and /jsonrpc endpoints are scheduled for removal (Odoo 22 / Odoo Online 21.1)
  2. Generate an API key from the user's Preferences > Account Security > New API Key
  3. Call the JSON-2 API endpoints using an Authorization: Bearer <api_key> header instead of the old login/password/uid flow
  4. Update calls that previously used execute_kw(db, uid, password, model, method, args) to the JSON-2 request/response shape
  5. Re-test any integration relying on session-based authentication, since JSON-2 replaces that with the bearer token scheme

Known gotchas

Related routes

Perform record CRUD via Odoo external API (XML-RPC or JSON-RPC)
Odoo External API · 5 steps · unrated
Authenticate and perform CRUD operations via Odoo XML-RPC external API
odoo · 5 steps · unrated
authenticate to odoo's external xml-rpc api using an api key instead of a password
odoo.com/documentation · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans