Connect and sync data with Odoo via RPC API

Odoo RPC API guides external applications through authenticating and calling Odoo models to read, create, update and delete records. It supports integration work in Python, JavaScript or curl, including automated import/export scripts and middleware between Odoo and another platform. You can describe a required integration or provide an error for diagnosis and a corrected call.

The examples distinguish XML-RPC API-key authentication from session-based web JSON-RPC. XML-RPC first authenticates through the common endpoint, checks that a user ID was returned and then calls models through the object endpoint. A search_read call retrieves selected fields from confirmed sale orders with a result limit, reducing the round trips of separate search and read calls.

Use it when connecting a Django, Node.js or mobile application to Odoo, moving data through scripts or investigating authentication and permission failures. Before selecting an endpoint, verify external API availability for the exact deployed version, hosting arrangement and subscription. Odoo Online and Odoo.sh are distinct offerings.

This skill does not implement OAuth2 or session login. The web dataset JSON-RPC fragment assumes an independently authenticated session cookie; an API key from the XML-RPC example does not establish that session. Choose the documented external API appropriate to the deployed version rather than treating the fragment as a complete login flow.

Mention @odoo-rpc-api with the integration requirement, language and relevant context, or submit an error to debug. Outputs are RPC call examples and explanations. The XML-RPC model call has this form after authentication and model proxy setup:

orders = models.execute_kw(db, uid, password,
    'sale.order', 'search_read',
    [[['state', '=', 'sale']]],
    {'fields': ['name', 'partner_id', 'amount_total'], 'limit': 10}
)

Record creation changes business data. Use an authorized test database and an approved integration user before adapting a create example. Keep API keys and session cookies out of logs and shared snippets.

Use API keys, available from Odoo 14+, instead of production passwords. Store credentials in environment variables or a secrets manager such as AWS Secrets Manager, and use a dedicated integration user with minimum permissions rather than master administrator credentials.

Batch requests and implement client-side throttling because the XML-RPC layer has no built-in rate limiting. Safe reads can use bounded backoff for connection failures. Reconcile an ambiguous create or write timeout using a stable external identifier before retrying, preventing duplicate business records. Attachments use authorized ir.attachment model calls with base64 binary fields; respect payload limits and access rules instead of treating JSON-RPC as a REST upload endpoint.