Usability - API Connector
This module provides a reusable framework for making outbound API calls from Odoo to external systems.
It ships three key components:
common.base.api - An abstract mixin that any Odoo model can inherit to gain the ability to send outbound API requests (XML-RPC or REST API), handle authentication, evaluate dynamic payloads, interpret responses with configurable result-mapping, send optional callbacks, and record every call in a dedicated log.
api.config - A configuration model where administrators define connection details such as endpoint URL, API type, HTTP method, authentication credentials, request headers, payload templates (Python expressions), and response-mapping rules (success key, success value, message key).
api.connector.log - A log model that stores the payload, response, status, calling user, and timestamp of every outbound API call for auditing and troubleshooting.
Table of contents
Usage
To use this method:
Go to menu Settings > Technical > Web Services > API Exports.
Create a new record and fill in the following fields:
API Name / Code - A human-readable name and a unique code used to look up the configuration programmatically (e.g. action_call_api('MY_CODE')).
Model - The Odoo model this configuration is related to (optional, informational).
Endpoint System - Choose Odoo to connect to another Odoo instance, or External for a generic REST service.
Endpoint URL - The base URL of the remote system (e.g. https://other-odoo.example.com).
Route Path - The path appended to the endpoint URL. For XML-RPC the default is /xmlrpc/2/object; for REST it is the specific route (e.g. /api/v1/products).
Callback URL - An optional URL that receives a POST callback after a successful API call.
API Type:
XML-RPC - Calls execute_kw on a remote Odoo instance. Requires Execute Model, Execute Method, and Execute Context.
REST API - Sends an HTTP request. Requires HTTP Method (GET / POST / PUT / DELETE) and optional Headers (a Python dict expression, e.g. {"Authorization": f"Bearer {auth_token}"}).
Authentication - Enable Auth Required and provide Database, Username, and Password. The module handles login automatically: for XML-RPC it obtains a uid, for REST API it obtains a session_id cookie. The token is cached on the configuration record and refreshed on expiry.
Disable SSL - Skips SSL certificate verification (development only).
Save Log - When enabled, every call creates an api.connector.log record regardless of success or failure.
Configure the JSON / Payload tab with a Python expression that evaluates to a dict or list. Available variables:
rec - the current record calling the API
env - the Odoo environment
today - fields.Date.context_today(self)
today_datetime - fields.Datetime.context_timestamp(self, now())
Example:
{"name": rec.name, "ref": rec.ref, "amount": rec.amount_total}For REST API, optionally configure the Params tab with a Python expression returning a dict of URL query parameters (e.g. {"page": 1, "lang": "th"}).
Configure Result Mapping to tell the module how to interpret the remote response:
Success Key - Dot-notation path to the success indicator (default is_success). Examples: result.is_success, 0.status.
Success Value - Expected string value that means success (e.g. True, ok, 200). Leave empty for a truthy check.
Message Key - Dot-notation path to the error message (default message). Example: error.message.value.
Click the Test API button on the configuration form to execute a test call. The result (or error) is displayed in the Test Result tab.
To add outbound API capability to your own model:
Inherit the common.base.api mixin:
class MyModel(models.Model): _name = "my.model" _inherit = ["my.model", "common.base.api"]Call the API by code:
self.action_call_api("MY_API_CODE")Override _hook_update_data to process the response:
def _hook_update_data(self, code_api, result): if code_api == "MY_API_CODE": # REST: result is the parsed JSON dict # XML-RPC: result is {"is_success": True, "result": <raw>} self.write({"external_id": result.get("id")})The mixin automatically handles authentication, request execution, error handling, status updates (api_status), and log creation.
Viewing Logs
Navigate to Settings > Technical > Web Services > Outbound API Logs to review all outgoing API call history. Each log entry records:
API code and name
Endpoint system
Source model and record ID
Status (Success / Failed / Draft)
Payload sent and response received
Error message (if any)
User who triggered the call and timestamp
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Saran Lim. <saranl@ecosoft.co.th>
Maintainers
Current maintainer:
This module is part of the ecosoft-odoo/ecosoft-addons project on GitHub.
You are welcome to contribute.
Metadata
Release files for odoo-addon-usability-api-connector 18.0.1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_usability_api_connector-18.0.1.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_usability_api_connector-18.0.1.1.3-py3-none-any.whl
| Download URL | odoo_addon_usability_api_connector-18.0.1.1.3-py3-none-any.whl |
|---|---|
| Size | 45.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8256b2b603d826e2447b55dd31d67a0f1fa3d0fe209d8192411b6dfa6c40e21e
|
|
BLAKE2b-256 checksum How to use checksums |
cb31a5b797d529340600c501e1c2e28bc990abef1d79ee245c26c93607a192ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-usability-api-connector 18.0.1.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.